Added
- Add
fallback
section to the ScaledObjects resources templates.
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
fallback
section to the ScaledObjects resources templates.In this release:
This release backports a fix for reducing IMDS Response Hop Limit to 2 if pod networking is in ENI mode to increase security. For clusters in ENI mode, all nodes are rolled when upgrading to this release.
This release backports a fix for reducing IMDS Response Hop Limit to 2 if pod networking is in ENI mode to increase security. For clusters in ENI mode, all nodes are rolled when upgrading to this release.
v0.1.78
(patch release)cluster
to v2.5.0.coredns
image to 1.12.2.trivy-operator
(app) to v0.11.1.trivy
(app) to v0.14.0.falco
(app) to v0.10.1.cloudnative-pg
(app) to v0.0.10.starboard-exporter
(app) to v0.8.2.cluster
to v2.5.0.kube-vip
to v0.9.2.coredns
image to 1.12.2.trivy-operator
(app) to v0.11.1.trivy
(app) to v0.14.0.falco
(app) to v0.10.1.cloudnative-pg
(app) to v0.0.10.starboard-exporter
(app) to v0.8.2.This release updates Kubernetes to the latest patch release v1.31.11.
During control plane upgrades, short-term warnings are now prevented by setting a fixed instead of dynamic AMI lookup string. This leads to nodes being rolled once when upgrading to this release.
We added an option to set the IMDSv2 request hop limit for EC2 instances ‒ this is usually not needed, except if security requirements such as AWS SCPs (service control policies) dictate a maximum.
Karpenter support keeps getting better: node-termination-handler is not installed anymore if only Karpenter node pools are used, as the same function is built into Karpenter (pod draining and EC2 instance termination handling). Nodes in such pools now also use the reduced IAM permission set (can be toggled in exceptional cases).
giantswarm.io/role: nodes
by default to private subnets used for nodes. Can be overwritten.cluster
to v2.5.0.node-termination-handler
when there are non-karpenter node pools because karpenter takes care of node drainingimageLookupFormat
to use a static string rather than CAPI replacing the OS and Kubernetes versions. This rolls control plane nodes.karpenter
worker nodes instance profile. This can be toggled back with global.providerSpecific.reducedInstanceProfileIamPermissionsForWorkers
.coredns
image to 1.12.2.MachinePool
CR, so the taint will be removed by CAPI.trivy-operator
(app) to v0.11.1.trivy
(app) to v0.14.0.falco
(app) to v0.10.1.cloudnative-pg
(app) to v0.0.10.starboard-exporter
(app) to v0.8.2.