Changed
- Removed check capabilities from VerticalPodAutoscaler resources.
- Dropped
CPUfrom Reports Controller VerticalPodAutoscaler controlled resources.
Changes and Releases
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Changed
- Removed check capabilities from VerticalPodAutoscaler resources.
- Dropped
CPUfrom Reports Controller VerticalPodAutoscaler controlled resources.
Fixed
- Fix applying RoleBindingTemplate to multiple namespaces
Fixed
- Fix applying RoleBindingTemplate to multiple namespaces
Highlights for the week ending August 31 2023
aws-load-balancer
- aws-load-balancer-controller-app version v1.3.4, migrates from monitoring labels to ServiceMonitor and introduces a new Pod Security Policy for Cluster API support (versions behind Kubernetes 1.25).
external-dns
- external-dns version v2.39.0 replaces monitoring labels with ServiceMonitor CR, adds minAllowed in VPA to avoid OOMs and increases memory limits.
kyverno
- kyverno-app version v0.15.1(and v0.15.0) updates to the highly anticipated Kyverno version 1.10.2. This release brings major architectural changes to the Kyverno controllers as well as breaking changes to the upstream Helm chart. During the upgrade to 0.15.0 or 0.15.1, existing Kyverno deployments will be briefly scaled to 0 and replaced with the new version. Important: The Helm schema has changed to reflect the new deployment structure, so if you are overriding Helm values, review the release notes and upgrade guide to ensure any relevant configuration will still apply to the new controllers. These changes include significant stability and performance improvements and VPA support for more Kyverno components.
linkerd
- linkerd2-cni version v1.1.0 upgrades to Linkerd v2.13.6.
- linkerd-control-plane version v1.1.0 upgrades to Linkerd v2.13.6.
- linkerd-viz version v1.3.0, upgrades to Linkerd v2.13.6 and brings better defaults for production environments and pod distribution budgets.
For more Information about the Linkerd v2.13.6 changes, please take a look at the official release notes
ingress-nginx
- We spent the last months reworking our ingress-nginx-app by aligning it to the upstream ingress-nginx project. This is necessary to be future-proof, feature compliant, and offer the best ingress experience possible. Therefore we want to announce the first public stable release of our new ingress-nginx chart.
This release includes breaking changes if you are currently using
v2.x.x. We set up a migration guide to make the upgrade as smooth as possible. Notable changes requiring your attention and/or manual intervention, like renaming, deprecating or removing values, have been highlighted below. Even though we highly recommend upgrading to this and future releases,v2.x.xwill continue receiving bug fixes as long as possible.
All feedback regarding this release, its changes, or our migration guide is very welcome!
Changed
- DNS Dashboard: add logs panel for CoreDNS
- Kong Connection Distribution: Make public
Changed
WARNING: this version requires Cilium to run because of the dependency on the CiliumNetworkPolicy CRD
- Upgrade dependency chart to 9.2.0.
- Adjusted the resource and limits to accomodate larger clusters by default
- Adjusted the admission controller to give it more QPS against the API
- Adjusted the updater to give it more QPS against the API
- Adjusted the recommender to give it
- more QPS against the API
- doubling the memory in case of an OOMKilled event
- Using the 95% percentile for the calculation of the CPU usage: should allow to scale up more precisely to account for spikes in CPU consumption of the workload
- Adjusted the resource and limits to accomodate larger clusters by default
- Calculating recommendations only for workloads which do have a VPA custom resource, instead of all workloads
- Removed standard network policies to decrease maintenance burden
- Fixed Cilium Network Policy to allow CRD jobs execution
- Added Cilium Network Policy weight for an early execution
- Disabled VPA for the updater pod otherwise it keeps on getting re-scheduled because the memory consumption varies a lot between reconsiling resources and idle
- Disabled VPA for the recommender pod otherwise it keeps on getting re-scheduled because the memory consumption varies a lot between reconsiling resources and idle
Changed
WARNING: this version requires Cilium to run because of the dependency on the CiliumNetworkPolicy CRD
- Upgrade dependency chart to 9.2.0.
- Adjusted the resource and limits to accomodate larger clusters by default
- Adjusted the admission controller to give it more QPS against the API
- Adjusted the updater to give it more QPS against the API
- Adjusted the recommender to give it
- more QPS against the API
- doubling the memory in case of an OOMKilled event
- Using the 95% percentile for the calculation of the CPU usage: should allow to scale up more precisely to account for spikes in CPU consumption of the workload
- Adjusted the resource and limits to accomodate larger clusters by default
- Calculating recommendations only for workloads which do have a VPA custom resource, instead of all workloads
- Removed standard network policies to decrease maintenance burden
- Fixed Cilium Network Policy to allow CRD jobs execution
- Added Cilium Network Policy weight for an early execution
- Disabled VPA for the updater pod otherwise it keeps on getting re-scheduled because the memory consumption varies a lot between reconsiling resources and idle
- Disabled VPA for the recommender pod otherwise it keeps on getting re-scheduled because the memory consumption varies a lot between reconsiling resources and idle
Fixed
- Remove
fallthroughfor reverse zones from kubernetes plugin.
- Remove
Fixed
- Remove
fallthroughfor reverse zones from kubernetes plugin.
- Remove