gardener / garden-setup

Describes Gardener components for installation of a Gardener landscape using sow
Other
78 stars 55 forks source link

[ci:component:github.com/gardener/gardener-extension-provider-azure:v1.38.1->v1.39.0] #1249

Closed gardener-robot-ci-1 closed 1 year ago

gardener-robot-ci-1 commented 1 year ago

Release Notes:

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 azure-cloud-node-manager -> `v1.25.20`
Always set the `vmType` in cloud-provider configuration files.
Updated quota exceeded error labeling 
Update `k8s.io/client-go` from `v0.26.3` to `v0.26.4` to resolve panic on health-checking special shoots.
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 
Included `UnavailableReplicas` in determining if a machine deployment status update is needed
Bump `k8s.io/*` deps to v0.27.2
updated image azure-cloud-node-manager -> `v1.27.10`
Add readiness check for snapshot validation webhook
updated image snapshot-controller -> `v6.3.1`
updated image livenessprobe -> `v2.11.0`
VM types with azure accelerated networking now work out-of-the-box with calico's ebpf dataplane.
An issue causing nil pointer panic on scaleup of the machinedeployment along with trigger of rolling update, is fixed
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.
updated image azure-cloud-controller-manager -> `v1.26.16`
updated image azure-cloud-controller-manager -> `v1.27.10`
updated image azure-cloud-node-manager -> `v1.28.2`
Updated to go v1.20.5
updated image azure-cloud-node-manager -> `v1.26.16`
`provider-azure` extension now supports [Shoot Force Deletion](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_operations.md#force-deletion). 
updated image csi-registrar -> `v2.9.0`
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-azure 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. 
Bastion instances now use the latest ubuntu server 22.04 LTS version 
updated image csi-resizer -> `v1.9.1`
updated image azure-cloud-controller-manager -> `v1.25.20`
`provider-azure` no longer supports Shoots or Seeds with Кubernetes version < 1.24.
A new make target is introduced to add license headers.
Removed dead metrics code and refactored the remaining metrics code
Added a new metric that will allow to get the number of stale (due to unhealthiness) machines  that are getting terminated
updated image csi-provisioner -> `v3.6.1`
An edge case where outdated DesiredReplicas annotation blocked a rolling update is fixed.
updated image azure-cloud-controller-manager -> `v1.28.2`
updated image csi-attacher -> `v4.4.1`
Force drain and delete volume attachments for nodes un-healthy due to `ReadOnlyFileSystem` and `NotReady` for too long
The following golang dependencies have been upgraded :
- `gardener/gardener` to `v1.80.3`
- `k8s.io/*` to `v0.28.2`
- `sigs.k8s.io/controller-runtime` to `v0.16.2`
gardener-robot commented 1 year ago

@gardener-robot-ci-1 Thank you for your contribution.