Skip to content

Latest commit

 

History

History
30 lines (20 loc) · 1.86 KB

BREAKING_CHANGES.md

File metadata and controls

30 lines (20 loc) · 1.86 KB
Raw

Breaking Changes

Version 2.0.0 [not released]

Required values

  • .Values.bitbucket.clustering.group is required for Bitbucket
  • .Values.bitbucket.mirror is required for Bitbucket
  • .Values.bitbucket.podManagementStrategy is required for Bitbucket
  • .Values.ingress.className is required for all products

securityContext format change

.Values.<product>.securityContext is now fully configurable with standard Kubernetes values.
In order to make this happen, we removed gid and enabled fields from securityContext stanza in values.yaml file. Instead, the standard fsGroup value is now the default parameter to make ensure the correct filesystem permissions. This setting is not necessary in OpenShift (or some other specific use cases).

Action required

  • If .Values.<product>.securityContext.enabled was set to true (the default value), set the existing .Values.<product>.securityContext.gid value to .Values.<product>.securityContext.fsGroup.
  • If .Values.<product>.securityContext.enabled was set to false, comment out all keys under .Values.<product>.securityContext.securityContext stanza. This means the .Values.<product>.securityContext should be empty.

Troubleshooting

If you encounter this error:

Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(StatefulSet.spec.template.spec.securityContext): unknown field "enabled" in io.k8s.api.core.v1.PodSecurityContext, ValidationError(StatefulSet.spec.template.spec.securityContext): unknown field "gid" in io.k8s.api.core.v1.PodSecurityContext]

It means your value.yaml file contains the unsupported enabled or gid values for the securityContext. Please follow the steps from securityContext change above.