v1.43.0
[gardener-extension-provider-aws]
⚠️ Breaking Changes
- [USER] The default VolumeSnapshotClass managed by
provider-awsdoes now properly define this VolumeSnapshotClass as default one. Previously there was a typo in the annotation value forsnapshot.storage.kubernetes.io/is-default-class, hence the VolumeSnapshotClass was never considered as default one by the external-snapshotter and the VolumeSnapshotClass defaulting was never working as expected. (gardener/gardener-extension-provider-aws#723, @ialidzhikov)- If you already deploy your own default VolumeSnapshotClass, then consider disabling provider-aws's default VolumeSnapshotClass (using the
storage.managedDefaultClassfield in the controlPlaneConfig) as having more than 1 default VolumeSnapshotClass will prevent external-snapshotter to default thespec.volumeSnapshotClassNameof a VolumeSnapshot.
- If you already deploy your own default VolumeSnapshotClass, then consider disabling provider-aws's default VolumeSnapshotClass (using the
✨ New Features
- [OPERATOR] The
csi-snapshot-validationService deployed by the provider-aws extension and the provider-aws'sgardener-extension-provider-awsService can now be topology-aware (depending on the Seed setting and the Shoot HA failure tolerance type). For more details, see the Topology-aware Traffic Routing documentation. (gardener/gardener-extension-provider-aws#703, @ialidzhikov) - [OPERATOR]
csi-driver-nodeis annotated with thewait-for-csi-nodeannotation. Gardener uses this to only schedule workload pods to aNodeonce the driver has been successfully registered with theCSINodeobject. (gardener/gardener-extension-provider-aws#716, @SimonKienzler)
🐛 Bug Fixes
- [OPERATOR] Fix an issue where
shootreconciliation would fail whensshAccesswas disabled. (gardener/gardener-extension-provider-aws#704, @AleksandarSavchev) - [OPERATOR] The stale healthcheck conditions from the extension are now properly cleaned up. (gardener/gardener-extension-provider-aws#724, @acumino)
- [OPERATOR] An issue has been fixed which caused undesired
PATCHrequests when updating the state in theWorkerorShootStateresources. (gardener/gardener-extension-provider-aws#729, @oliver-goetz) - [OPERATOR] An issue causing provider-aws to wrongly delete the
extensions.gardener.cloud:provider-aws:csi-snapshot-validationClusterRole and ClusterRoleBinding from the Seed cluster on every Shoot deletion is now fixed. (gardener/gardener-extension-provider-aws#735, @ialidzhikov)
🏃 Others
- [OPERATOR] Added
cloudproviderwebhook part ofgardener-extension-provider-awswhich ensures that thecloudprovidersecret has thecredentialsFilefield present. The format of this field can be found in this documentation. (gardener/gardener-extension-provider-aws#683, @AleksandarSavchev) - [OPERATOR] The
cloud-controler-managerandcsi-driver-controllerdeployments now use an AWS credentials file for authentication. (gardener/gardener-extension-provider-aws#683, @AleksandarSavchev) - [OPERATOR] Add support for IMDSv2 (gardener/gardener-extension-provider-aws#709, @kon-angelo)
- [OPERATOR] Adapted extension components to support the FullNetworkPoliciesInRuntimeCluster feature gate introduced by
gardener/gardenerv1.66, see here and #7352 for more information. (gardener/gardener-extension-provider-aws#714, @rfranzke) - [OPERATOR] aws-ebs-csi-driver has been updated
v1.14.1 -> v1.17.0(gardener/gardener-extension-provider-aws#721, @kon-angelo) - [OPERATOR] cloud-controller-manager has been updated
v1.26.0 -> v1.26.1(gardener/gardener-extension-provider-aws#721, @kon-angelo) - [OPERATOR] Fix an issue that allows duplicate zones in the infrastructure. (gardener/gardener-extension-provider-aws#726, @kon-angelo)
- [OPERATOR] The
gardener-extension-admission-awsService in thegardener-extension-admission-awschart can now be configured to be topology-aware. (gardener/gardener-extension-provider-aws#732, @ialidzhikov)
[aws-custom-route-controller]
🏃 Others
- [OPERATOR] Bump golang.org/x/net from 0.2.0 to 0.7.0 (gardener/aws-custom-route-controller#10, @dependabot[bot])
- [OPERATOR] Bump builder image from
golang:1.19.5togolang:1.20.2(gardener/aws-custom-route-controller#11, @MartinWeindel)
[machine-controller-manager]
🐛 Bug Fixes
- [USER] An edge case where all the machineSets were scaled down to zero has been dealt with. (gardener/machine-controller-manager#804, @himanshu-kun)
[machine-controller-manager-provider-aws]
⚠️ Breaking Changes
- [DEPENDENCY]
KeyNameinAWSProviderSpecstruct has been changed to apointer. (gardener/machine-controller-manager-provider-aws#104, @AleksandarSavchev)
✨ New Features
- [OPERATOR] added support to modify instance metadata parameters for a VM through machineClass only during creation. This could be used to enable instance metadatav2 to containerised environment (gardener/machine-controller-manager-provider-aws#105, @kon-angelo)
🏃 Others
- [OPERATOR] Dropped validation for
KeyNameinAWSProviderSpec. (gardener/machine-controller-manager-provider-aws#104, @AleksandarSavchev) - [OPERATOR] CVE categorization for mcm-provider-aws has been added. (gardener/machine-controller-manager-provider-aws#108, @dkistner)
[terraformer]
🏃 Others
- [OPERATOR] Update TF_VERSION
0.15.5->1.3.9and update how the local providers are fetched and stored to be compatible with the latest TF specification. (gardener/terraformer#133, @kon-angelo)