0.39.0

Release date: September 01, 2022

The configuration of the Ingress within the Helm chart has been changed.

Prior to this version the annotations and paths of the Ingress where hard-coded which prevented the chart to be deployed on other platforms then AWS.

From this version onwards, the AWS specific annotations and paths have been removed. Using the Helm values it is now possible to defined annotations and paths as needed.

With this change, the value envConfig.routing.ingressScheme has also been removed which was used to customize the alb.ingress.kubernetes.io/scheme annotation.

To use the annotations and paths defined prior to this change, set the following into the custom values file:

envConfig:
  routing:
    annotations:
      # see: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/ingress/annotations/
      kubernetes.io/ingress.class: alb
      alb.ingress.kubernetes.io/scheme: "internet-facing"
      alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
      alb.ingress.kubernetes.io/ssl-policy: 'ELBSecurityPolicy-TLS-1-2-2017-01'
      alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig": 
        { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'

    extraPaths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: ssl-redirect
            port:
              name: use-annotation

The configuration of the external database and its credentials within the Helm chart has been changed.

Prior to this version, the password which was used to authenticate against the database was directly specified as a Helm value. This is bad design and has some security implications like saving the password in plaintext within the value files.

It has been changed so that the password is provided by a K8s secret which needs to be created by an administrator prior to the deployment.

To migrate, follow these steps and edit your custom Helm values file:

1. Copy the value of envConfig.database.password which is the current database password
2. Create the K8s secret object, replacing the <namespace> and <postgres-password> placeholders:

   kubectl -n <namespace> create secret generic w3syse-postgresql-password \
   --from-literal=postgresql-password="<postgres-password>"
   

3. Adjust the Helm values to reflect the changes:

   envConfig:
     database
       password:
         secret: "w3syse-postgresql-password"
         key: "postgresql-password"