Managed Apps
This release upgrades kong to release 3.1.1 which contains breaking changes. Please consider reading the upstream Breaking changes documentation before upgrading. Users of the kong enterprise should read the Kong Gateway changelogs of releases 3.0.0.0 onwards up to 3.1.1.3.
Updates
- Align with upstream chart version 2.16.2 (Changes in upstream repository)
- Update kong/kong to 3.1.1. Please read Breaking changes notes
- Execute enterprise tests with kong-gateway container image version 3.1.1.3-debian
- Update kong ingress controller to 2.8.1
- Update custom resource definitions to those used by kong ingress controller [2.8.1]
Changes
- Breaking The
minReadySecondsvalue previous found atdeployment.kong.minReadySecondsis now configured at pathdeployment.minReadySeconds. - Increase default requests/limits to 1 cpu and 2G memory
- Remove startupProbe from kong ingress controller. More information
Added
- Add support for
VPAfor core, cert-controller and webhook deployments, enabled by default
- Add support for
Changed
- Push
Jiralertapp to GiantSwarm catalog.
- Push
Changed
- Upgraded upstream chart from 3.2.1 to 4.4.2 - see changelog for more information.
- upgraded Loki from 2.6.1 to 2.7.2 - see changelog for more information.
- ⚠️ breaking changes
- nginx file definition for loki-multi-tenant has moved to a helper template.
- sample configs: updated schema version to v12 (brings performance improvements for S3 - see https://grafana.com/blog/2022/04/11/new-in-grafana-loki-2.5-faster-queries-more-log-sources-so-long-s3-rate-limits-and-more/)
- azure sample values fixed
- doc improvements
Added
- Align to upstream: Allow configuring the default backend.
Added
- Add support for additional environment variables
Changed
- Add acme annotation only if letsencrypt is explicitly enabled which should make it possible to use other cert-issuers without having conflicting annotation values
Changed
- Renamed
falco-apptofalco.
- Renamed
Changes
- Add instance label to default topologySpreadConstraints label selector
- Update kong/kubernetes-ingress-controller to 2.8.1.
- Suggest using giantswarm/kong-gateway:2.8.2.3-debian as enterprise container image.
- Use
/readyzpath for ingress controller readiness check. - Update kubernetes api token secret with projected volume. This should fix problems with empty or expired ServiceAccount tokens.