Upgrading or Uninstalling SecureAuth Helm Charts

No breaking changes. Helm charts were updated to match SecureAuth version.

Dependency redis helm chart was replaced by redis-cluster helm chart. The old redis instances will be destroyed in favour of new redis-cluster. Data migration is not supported but could be done manually which is out of the scope of this chart.

Version 0.15.1 of SecureAuth kube stack helm chart uses docker.cloudentity.io as the secret name referencing SecureAuth registry. If you're using the artifactory and haven't overridden imagePullSecrets before, you have to create a new secret with the name docker.cloudentity.io.

See Docker Pull Credentials.

Due to bug in SecureAuth, redis-cluster implementation was reverted back to redis helm chart. Redis multi-master instances will be destroyed and recreated as master-replica. Data migration is not supported but could be done manually which is out of the scope of this chart.

Version 0.15.1 of SecureAuth kube stack helm chart uses docker.cloudentity.io as the secret name referencing SecureAuth registry. If you're using the artifactory and haven't overridden imagePullSecrets before, you have to create a new secret with the name docker.cloudentity.io.

See Docker Pull Credentials.

Dependency redis helm chart was replaced by redis-cluster helm chart. The old redis instances will be destroyed in favour of new redis-cluster. Data migration is not supported but could be done manually which is out of the scope of this chart.

Version 1.10.0 of SecureAuth changes key names in feature flags from camelCase to snake_case in values.yaml.

A major chart version change (for example, v 1.2.3 -> v 2.0.0) indicates that there is an incompatible breaking change that requires manual actions.