Added
- Included the
giantswarm.io/clusterlabel
giantswarm.io/cluster labelWe’re going back to installing the kong OSS version by default instead of enterprise. In case you’re relying on this default behaviour, please make sure to set the .Values.image.repository, .Values.image.tag, .Values.enterprise.enabled and .Values.enterprise.license_secret values to the respective Enterprise values.
These changes were introduced in PRs #378 and #379.
This release drops support for Kubernetes below v1.26.
.Values.kubectlApplyJob.files to any other file in helm/kong-app/crds/ folder. The default is crds/custom-resource-definitions-v3.4.3.yaml.coredns image to 1.12.1.Depending on your current setup, this release may contain breaking changes. We go into these in more detail below and therefore ask you to read them carefully and check whether and to what extent they affect your setup.
controller.progressDeadlineSeconds.controller.unhealthyPodEvictionPolicy.controller.metrics.prometheusRule.annotations.controller.metrics.service.enabled.defaultBackend.maxUnavailable.defaultBackend.unhealthyPodEvictionPolicy.--enable-annotation-validation CLI flag is already enabled by default in this app since v3.2.0.allow-cross-namespace-resources ConfigMap option getting deactivated affects you if you are currently referencing resources such as Secrets in Ingress resource annotations from namespaces other than the Ingress resource itself.annotations-risk-level ConfigMap option getting lowered to High affects you if you are currently using annotations with an annotation risk level of Critical. Especially snippet annotations belong to this annotation risk level. So even though you activated snippet annotations via ConfigMap option in the past, you now also need to increase the annotations-risk-level ConfigMap option back to Critical.strict-validate-path-type ConfigMap option is already enabled by default in this app since v3.2.0.image to global.image.configmap.configmap value is deprecated since v3.0.0. Please use controller.config instead.giantswarm.io/monitoring_basic_sli label.unhealthyPodEvictionPolicy of the generated PodDisruptionPolicy. Default is IfHealthyBudgetkubectlApplyJob.enabled to falseDepending on your current setup, this release may contain breaking changes. We go into these in more detail below and therefore ask you to read them carefully and check whether and to what extent they affect your setup.
controller.progressDeadlineSeconds.controller.unhealthyPodEvictionPolicy.controller.metrics.prometheusRule.annotations.controller.metrics.service.enabled.defaultBackend.maxUnavailable.defaultBackend.unhealthyPodEvictionPolicy.--enable-annotation-validation CLI flag is already enabled by default in this app since v3.2.0.allow-cross-namespace-resources ConfigMap option getting deactivated affects you if you are currently referencing resources such as Secrets in Ingress resource annotations from namespaces other than the Ingress resource itself.annotations-risk-level ConfigMap option getting lowered to High affects you if you are currently using annotations with an annotation risk level of Critical. Especially snippet annotations belong to this annotation risk level. So even though you activated snippet annotations via ConfigMap option in the past, you now also need to increase the annotations-risk-level ConfigMap option back to Critical.strict-validate-path-type ConfigMap option is already enabled by default in this app since v3.2.0.image to global.image.configmap.configmap value is deprecated since v3.0.0. Please use controller.config instead.giantswarm.io/monitoring_basic_sli label.coredns image to 1.12.0.