3.0.0

Release notes

Important

Breaking changes

This realease introduces several breaking changes. Make sure to adjust your HelmRelease files to use this version

What's Changed

Volumes handling

This release changes how volumes should be configured. At this point we support three type of volumes:

• nfs
• secret
• configmap

Every type of volume has it's own mountPath and subPath parameters.

Warning

NFS configuration is moved one level up in HelmRelease structure, during the type object removal. Be sure, to follow the provided NFS example on upgrade.

NFS example:

volumes:
  ownership: 991:991
  nfs:
    server: srv-storage.lan
    path: /storage
    mountPath:
    - data:/data

Upgrading

Before version 3.0.0

volumes:
  enabled: true
  mountPath:
    - model-cache:/cache
  ownership: 0:0
  type:
    nfs:
      server: nfs.lan
      path: /storage

On version 3.0.0

volumes:
  ownership: 0:0
  nfs:
    server: nfs.lan
    path: /storage
    mountPath:
    - model-cache:/cache

Service name

Previous version of this HelmChart has service name prefixed with ReleaeName value. This turned out to be a little bit confusing how service should be named when this name should be referenced in other app. This approach was replaced with static service name

Example:

services:
  - name: app-web
    protocol: "TCP"
    servicePort: 8080
    targetPort: 80

What's added

Configmap volumes

This feature allow to mount files in configmap inside container.

Configmap example:

volumes:
  configmap:
    configMap: application-config
    mountPath: /app/config.json
    subPath: config.json

Secret volumes

This new feature allows to mount secret as a file inside container.

Secret Example

volumes:
  secret:
    secretName: application-secret
    mountPath: /app/secret.json
    subPath: secret.json

What's removed

dbsecrets

This resource was used to generate app-related database secret. It's no longer needed since SOPS was introduced as the way to provide encrypted secret data

initwebsitedir

This webhook was removed to the execution problems. It was responsible for creating directory structure on NFS share for deployed application. This hook was executed before helm, install process. Perhaps this feature will be restored in future versions. For now it was removed due to app deployment disruption.

Mattermost-notify

This webhook was executed to notify users, that application is deployed on kubernetes cluster. It turned to be not useful as i thought.

MySQLDBHelper

This webhoo along with dbsecrets was developed to create database for application. It was not maintained anymore. It's support MySQL databases only, so it's not so useful anymore.