3.56.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.74.2 by @Diaphteiros [#1261]

3.55.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.73.2 by @Diaphteiros [#1260]

3.54.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.72.2 by @Diaphteiros [#1259]

3.53.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.71.6 by @Diaphteiros [#1258]

3.52.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.70.2 by @Diaphteiros [#1257]

🏃 Others

• [OPERATOR] Since the seeds seem to take a lot longer to become ready since a few Gardener releases, the timeout for this has been increased. by @Diaphteiros [#1257]

3.51.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.69.3 by @Diaphteiros [#1229]

3.50.0

[gardener/garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.68.1 by @Diaphteiros [#1208]

3.49.0

[gardener/garden-setup]

⚠️ Breaking Changes

• [OPERATOR] ⚠️ The previously used cert-manager has been exchanged for the Gardener cert-manager. Simply deploying over an existing landscape won't work with this release. The best idea is probably to remove the old cert-manager first before deploying the new one:

  • manually edit garden-setup and remove all references to cert-manager/* from all components (except the cert-manager components itself)
    • these references can be found under component.imports in the respective component's component.yaml file
  • remove the old cert-manager: sow delete cert-manager/cert cert-manager/solver cert-manager/controller
    • if it complains about some components which depend on the component still being installed, you missed a reference in the first step
  • upgrade garden-setup to this release (which will also revert your changes to the dependencies)
  • deploy everything again: sow deploy -A

  Note that this is will create new certificates for the dashboard ingress.
  This is just a proposal which is likely to work - garden-setup does not support upgrades of existing landscapes and the previously suggested migration path is not tested. by @Diaphteiros [#1076]

✨ New Features

• [OPERATOR] The recommended sow version to use with garden-setup is now 3.8.0. by @Diaphteiros [#1206]
• [OPERATOR] Upgrade Gardener to v1.67.2 by @Diaphteiros [#1202]

🐛 Bug Fixes

• [OPERATOR] Apparently, kubectl version returned a minor version with a + suffix for some k8s implementations, which garden-setup couldn't handle. The k8sversion component, which fetches the cluster versions, now removes this suffix, if it exists. by @Diaphteiros [#1203]

🏃 Others

• [OPERATOR] Upgrade Gardener extension runtime-gvisor to v0.11.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension provider-vsphere to v0.31.2 by @Diaphteiros [#1202]
• [OPERATOR] ⚠️ Since Gardener now automatically deploys NetworkPolicy resources into the gardener namespace of a seed - which messes up the communication on the base cluster - the network policies deployed by garden-setup itself had to be modified: if the network policies are activated, garden-setup will now deploy an additional allow-all-ingress policy, allowing all ingress traffic in the base cluster's garden namespace. If the network policies are deactivated, garden-setup instead uses an allow-all policy that simply allows all egress and ingress traffic in the garden namespace. There are no changes required, unless you are actively working with network policies in the base cluster's garden namespace. by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension provider-openstack to v1.36.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension shoot-cert-service to v1.36.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener cert-manager to v0.11.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension shoot-dns-service to v1.38.1 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener dns-controller-manager to v0.15.8 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension networking-calico to v1.36.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension os-gardenlinux to v0.20.0 by @Diaphteiros [#1202]
• [OPERATOR] ⚠️ Due to some changes in Gardener's certificate handling, the ingress certificate changed slightly: instead of just using the wildcard ingress domain as Common Name, it now uses the dashboard's domain as CN and has the wildcard ingress domain configured as SAN. There are no changes required, unless you are interacting with the ingress certificate in some way and rely on its CN value. by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension os-ubuntu to v1.22.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener Dashboard to v1.68.2 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension provider-aws to v1.46.0 by @Diaphteiros [#1202]
• [OPERATOR] Default k8s versions and machine image versions have been upgraded. by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension provider-gcp to v1.32.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension suse-chost to v1.22.0 by @Diaphteiros [#1202]
• [OPERATOR] Upgrade Gardener extension provider-azure to v1.38.1 by @Diaphteiros [#1202]

3.48.0

[garden-setup]

⚠️ Breaking Changes

• [OPERATOR] The PodDisruptionBudget resource in the virtual apiserver chart has been upgraded to v1. This might cause problems with old k8s versions. (#1066, @Diaphteiros)
• [OPERATOR] ⚠️ The installation method for the terminal-controller-manager has changed significantly. Deploying over an existing landscape where the terminals component is active (it's deactivated by default) with this new version will most likely not work. For upgrading an existing landscape with active terminals, it's recommended to first remove the component (sow delete -a terminals (WARNING: this will also remove the dashboard component)), then upgrade to this version of garden-setup and then deploy it again. (#1066, @Diaphteiros)

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.66.2 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener to v1.65.2 (#1034, @Diaphteiros)
• [OPERATOR] garden-setup will now provide the cluster's version to helm template calls via the --kube-version flag. This has a few side effects: (#1039, @Diaphteiros)
  • There is a new component called k8sversion. It's a dummy component, which doesn't actually deploy anything, but it fetches each pre-existing cluster's (= base cluster and potential soils) k8s version instead.
  • After deployment of the virtual kube-apiserver, the export generation now waits until it is ready, so it can fetch its k8s version.
  • ⚠️ Since helm might deploy different manifests for different k8s versions, this change means that the result of sow deploy now also depends on the k8s versions of all clusters in landscape.iaas.
  • Re-running sow deploy after upgrading the base cluster to a higher k8s version could therefore lead to changes.
  • This could be prevented by not re-running the k8sversion component, as that one is responsible for fetching the k8s versions. Most of the time, deploying the helm chart fitting to the cluster is probably desired, though.

🐛 Bug Fixes

• [OPERATOR] The previously mentioned race condition which could prevent the deletion of Azure seeds is now fixed. (#1034, @Diaphteiros)

🏃 Others

• [OPERATOR] Upgrade Gardener terminal-controller-manager to v0.25.0 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-vsphere to v0.26.0 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension shoot-cert-service to v1.30.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension shoot-dns-service to v1.31.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-azure to v1.34.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension runtime-gvisor to v0.9.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-gcp to v1.28.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-aws to v1.42.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-openstack to v1.32.1 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension networking-calico to v1.31.2 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension os-gardenlinux to v0.19.0 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension os-suse-chost to v1.21.0 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension os-ubuntu to v1.21.0 (#1066, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-vsphere to v0.25.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension shoot-cert-service to v1.29.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-aws to v1.42.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension shoot-dns-service to v1.30.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-gcp to v1.28.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-azure to v1.34.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension runtime-gvisor to v0.9.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension networking-calico to v1.31.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener extension provider-openstack to v1.32.0 (#1034, @Diaphteiros)
• [OPERATOR] Upgrade Gardener DNS controller manger to v0.15.2 (#1034, @Diaphteiros)
• [OPERATOR] S3 buckets created in the etcd/backupinfra component are now private. (#1054, @Diaphteiros)

3.47.0

[garden-setup]

✨ New Features

• [OPERATOR] Upgrade Gardener to v1.64.1 (gardener/garden-setup#1017, @Diaphteiros)
• [OPERATOR] Upgrade Gardener Dashboard to 1.67.0 (gardener/garden-setup#1017, @Diaphteiros)
• [OPERATOR] ⚠️ There is a new sow version available (3.7.0). It's recommended to upgrade sow to this version, as it fixes a bug which can lead to wrong imageVectorOverwrites for the seed clusters. (gardener/garden-setup#1017, @Diaphteiros)

🏃 Others

• [OPERATOR] Upgrade default k8s versions and machine images. (gardener/garden-setup#1017, @Diaphteiros)
• [OPERATOR] Upgraded the AWS terraform provider. This might cause problems when upgrading an existing landscape - deleting the gen/etcd/backupinfra folder should solve this. (gardener/garden-setup#1017, @Diaphteiros)