Connectivity
Added
- Included the
giantswarm.io/cluster
label
- Included the
We’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.Added
- Allow chart users to specify the version of the CRDs to match the kong ingress controller version by changing
.Values.kubectlApplyJob.files
to any other file inhelm/kong-app/crds/
folder. The default iscrds/custom-resource-definitions-v3.4.3.yaml
.
Changed
- Update kong ingress controller to 3.4.3
- Align with upstream chart version 2.48.0 (Changes in upstream repository)
- Allow chart users to specify the version of the CRDs to match the kong ingress controller version by changing
Changed
- Update
coredns
image to 1.12.1.
- Update
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.
Added
- Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
- Deployment: Add
controller.progressDeadlineSeconds
. - Pod Disruption Budget: Add
controller.unhealthyPodEvictionPolicy
. - Prometheus Rule: Add
controller.metrics.prometheusRule.annotations
. - Metrics Service: Add
controller.metrics.service.enabled
. - Default Backend: Add
defaultBackend.maxUnavailable
. - Default Backend: Add
defaultBackend.unhealthyPodEvictionPolicy
.
- Deployment: Add
Changed
- Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
- Controller: Update image to v1.12.0.
NOTE: Please read the upstream changelog carefully, especially the entries marked with ⚠️. In addition, the following should be noted:- The
--enable-annotation-validation
CLI flag is already enabled by default in this app since v3.2.0. - The
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. - The
annotations-risk-level
ConfigMap option getting lowered toHigh
affects you if you are currently using annotations with an annotation risk level ofCritical
. 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 theannotations-risk-level
ConfigMap option back toCritical
. - The
strict-validate-path-type
ConfigMap option is already enabled by default in this app since v3.2.0.
- The
- Values: Rename
image
toglobal.image
.
- Controller: Update image to v1.12.0.
- Chart: Sync to upstream. (#788)
- Controller: Update image to v1.12.1.
- Kube Webhook CertGen: Update image to v1.5.2.
Removed
- Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
- Chart: Remove Pod Security Policies.
NOTE: Pod Security Policies have already been removed from Kubernetes in v1.25. Therefore, this version is not compatible with Kubernetes v1.24 and below. - Values: Remove
configmap
.
NOTE: Theconfigmap
value is deprecated since v3.0.0. Please usecontroller.config
instead. - Deployment: Remove
giantswarm.io/monitoring_basic_sli
label. - Deployment: Remove OpenTelemetry init container.
NOTE: OpenTelemetry is still supported, but since the module is built into the controller image since v1.10, we hereby remove the init container and image which were used to install it upon controller startup.
- Chart: Remove Pod Security Policies.
- Chart: Sync to upstream. (#768https://github.com/giantswarm/ingress-nginx-app/pull/768)
Changed
- Update architect-orb and ATS.
- Add DNSEndpoints as a source for DNS records.
Added
- Allow users to change the
unhealthyPodEvictionPolicy
of the generated PodDisruptionPolicy. Default isIfHealthyBudget
- Allow users to disable CRD installation Job by setting
kubectlApplyJob.enabled
tofalse
- Allow users to change the
Added
- Allow selecting channel (“standard” or “experimental”) for each individual CRD
Changed
- Upgrade Gateway API CRDs to v1.2.1