Force drain and delete volume attachments for nodes un-healthy due to `ReadOnlyFileSystem` and `NotReady` for too long
A new make target is introduced to add license headers.
Add documentation for the "flow" infrastructure reconciler.
updated image csi-provisioner -> `v3.6.0`
All chart deployments are now using `embed.FS` instead of the filesystem.
The following golang dependencies have been upgraded :
- `gardener/gardener`: `v1.81.0`->`v1.81.6`
- `k8s.io/*`: `v0.28.2`-> `v0.28.3`
- `sigs.k8s.io/controller-runtime`: `v0.16.2`-> `v0.16.3`
Logs for confirming eventual consistency are exposed. This helps to know if such check was successful or not.
The `aws-load-balancer-controller` deployment now uses an AWS credentials file for authentication.
Removes `node.machine.sapcloud.io/not-managed-by-mcm` annotation from nodes managed by the MCM.
The registry of the aws-ebs-csi-driver image is switched from ECR (`public.ecr.aws`) to `registry.k8s.io` because the ECR does not support image pulls over IPv6.
Updated to go v1.20.5
status.Status now captures underline cause, allowing consumers to introspect the error returned by the provider. WrapError() function could be used to wrap the provider error
Remove dependency to specific calico and cilium versions.
updated image livenessprobe -> `v2.11.0`
State update for a Worker object can be now skipped by annotating it with `worker.gardener.cloud/skip-state-update=true`.
`provider-aws` extension now supports [Shoot Force Deletion](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_operations.md#force-deletion).
Update external-snapshotter to v6.3.1
No caching of secrets
The following dependency is updated:
- github.com/gardener/gardener: v1.77.5 -> v1.80.3
- k8s.io/* : v0.26.4 -> v0.28.2
- sigs.k8s.io/controller-runtime: v0.14.6-> v0.16.2
Added a new metric that will allow to get the number of stale (due to unhealthiness) machines that are getting terminated
Removed dead metrics code and refactored the remaining metrics code
The default `machine-safety-orphan-vms-period` has been reduced from 30m to 15m.
Makefile targets have changed: Introduced gardener-setup, gardener-restore, gardener-local-mcm-up, non-gardener-setup, non-gardener-restore, non-gardener-local-mcm-up. Users can also directly use the scripts which are used by these makefile targets.
An edge case where outdated DesiredReplicas annotation blocked a rolling update is fixed.
Bump `k8s.io/*` deps to v0.27.2
New metrics introduced:
- api_request_duration_seconds -> tracks time taken for successful invocation of provider APIs. This metric can be filtered by provider and service.
- driver_request_duration_seconds -> tracks total time taken to successfully complete driver method invocation. This metric can be filtered by provider and operation.
- driver_requests_failed_total -> records total number of failed driver API requests. This metric can be filtered by provider, operations and error_code.
The provider-aws extension does now support shoot clusters with Kubernetes version 1.28. You should consider the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.28.md) before upgrading to 1.28.
An issue causing nil pointer panic on scaleup of the machinedeployment along with trigger of rolling update, is fixed
updated image aws-ebs-csi-driver -> `v1.23.0`
Add new unit tests.
Included `UnavailableReplicas` in determining if a machine deployment status update is needed
Update aws-ebs-csi-driver to `v1.22.0`
Added `errorCode` field in the `LastOperation` struct. This should be implemented only for the `CreateMachine` call in the `triggerCreationFlow`. This field will be utilized by Cluster autoscaler to do early backoff
The following golang dependencies have been upgraded :
- `gardener/gardener`: `v1.81.6`->`v1.83.2`
Update volume-modifier-for-k8s to `v0.1.2`
`provider-aws` no longer supports Shoots or Seeds with Кubernetes version < 1.24.
updated image csi-resizer -> `v1.9.0`
MCM status code `ResourceExhausted` is now utilized in mcm-provider-aws.
Release Notes: