v1.10.2

[gardener-extension-provider-alicloud]

Improvements

• [OPERATOR] An issue preventing extensionsv1alpha1.BackupEntry to be deleted is now fixed. (df17937)

v1.11.0

[gardener-extension-provider-alicloud]

Improvements

• [OPERATOR] The kubelet environment is now extended with PROVIDER_ID variable. This is necessary to avoid usage of tightly customized images. (#89, @jia-jerry)

[gardener]

Improvements

• [OPERATOR] Fixed a bug that lead to omitting the details message why a health check failed when writing the Extension CRD conditions. (gardener/gardener#2394, @danielfoehrKn)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.11.0
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.11.0

v1.10.1

[gardener]

Improvements

• [OPERATOR] Fixed a bug that lead to omitting the details message why a health check failed when writing the Extension CRD conditions. (gardener/gardener#2394, @danielfoehrKn)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.10.1
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.10.1

v1.10.0

[gardener-extension-provider-alicloud]

Improvements

• [OPERATOR] ClusterRoles for the machine-controller-manager that might be orphaned now as they created with an earlier, buggy version of this controller are now cleaned up during startup. (#86, @rfranzke)
• [OPERATOR] The pre-defined ValidatingWebhookConfiguration assets now set sideEffects=None. This enables dry-run related operations, like kubectl diff, for core.gardener.cloud resources. (#75, @timuthy)

[gardener]

Improvements

• [USER] The generic Worker actuator does now exit its reconciliation flows early if it detects an error during the machine reconciliation. This allows to faster propagate problems to the end-user. (gardener/gardener#2348, @rfranzke)
• [USER] The extension health check library does now allow individual health checks to return the Progressing status. This allows to provide more accurate status information and less false negative health reports. (gardener/gardener#2289, @rfranzke)
• [OPERATOR] The Gardenlet sets an additional annotation to Extension CRDs during reconciliation to guarantee an update event for the watching clients. (gardener/gardener#2290, @danielfoehrKn)
• [OPERATOR] Fixes a bug in the extension libraries that could lead to duplicate reconciliation of extension resources. When respecting the operation annotation set by the Gardenlet during reconciliation, extension controllers now only watch the Extension CRD. (gardener/gardener#2290, @danielfoehrKn)
• [OPERATOR] Fixes a bug in the extension library of all extension resources that lead to not stopping the reconciliation of extension resources when the Shoot is in 'failed' state (Shoot.Status.lastOperation.state = Failed). (gardener/gardener#2279, @danielfoehrKn)
• [OPERATOR] Fixed a bug in the health check library that leads to too many health checks being executed when the Extension.Status changes. (gardener/gardener#2307, @danielfoehrKn)
• [OPERATOR] Fixed the health check condition.lastTransitionTime in the health check library. (gardener/gardener#2307, @danielfoehrKn)

[machine-controller-manager]

Improvements

• [USER] Azure: Add support for custom image plans for VMs in CCM (gardener/machine-controller-manager#463, @MSSedusch)
• [USER] Provide a way to specify "auth-extra-groups" field in created bootstrap tokens. (gardener/machine-controller-manager#442, @zuzzas)
• [USER] Support multiple network interfaces in the AWS driver (gardener/machine-controller-manager#441, @zuzzas)
• [OPERATOR] The mcm stopped adopting Nodes with empty ProviderID field (gardener/machine-controller-manager#451, @zuzzas)
• [OPERATOR] Bugfix: Continue with VM deletion when data disk doesn't exist for AWS. (gardener/machine-controller-manager#447, @prashanth26)
• [OPERATOR] Add GCP local ssd disk support (gardener/machine-controller-manager#414, @tennix)
• [DEVELOPER] Added support for multiple Data Disks in Azure and AliCloud. (gardener/machine-controller-manager#397, @guydaichs)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.10.0
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.10.0

v1.9.1

[gardener]

Improvements

• [OPERATOR] Fixed a bug in the health check library that leads to too many health checks being executed when the Extension.Status changes. (gardener/gardener#2307, @danielfoehrKn)
• [OPERATOR] Fixed the health check condition.lastTransitionTime in the health check library. (gardener/gardener#2307, @danielfoehrKn)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.9.1
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.9.1

v1.9.0

[gardener-extension-provider-alicloud]

Improvements

• [OPERATOR] Fixed a bug in the healthcheck library that prevents checks after a Shoot has been woken up from hibernation. Gardener extensions require a minor change during the healthcheck registration. (#73, @ialidzhikov)
• [OPERATOR] Golang version is updated to 1.14.2. (#70, @ialidzhikov)
• [OPERATOR] Fix issue #12 cannot delete infra when credentials are invalid on alicloud (#69, @minchaow)

[gardener]

Improvements

• [DEVELOPER] The ShootNotFailed predicate in the extensions library does now work as expected. (gardener/gardener#2265, @rfranzke)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.9.0
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.9.0

v1.8.0

[gardener-extension-provider-alicloud]

Most notable changes

• [USER] The Alicloud extension does now support shoot clusters with Kubernetes version 1.18. You should consider the Kubernetes release notes before upgrading to 1.18. (#58, @rfranzke)

Improvements

• [USER] Now user does not need to maintain Zone filed of controlPlaneConfig in Shoot resource. And also, controlPlaneConfig is not needed. (#64, @jia-jerry)
• [OPERATOR] Zone filed of controlPlaneConfig is removed from Shoot. (#64, @jia-jerry)
• [OPERATOR] Alicloud provider now allows setting minimum=0 for worker pools in the Shoot. (#62, @minchaow)
• [OPERATOR] g/gardener-extensions does now require the g/[email protected]. (#48, @ialidzhikov)

[gardener-extensions]

Improvements

• [OPERATOR] Add Separate sidecar controller to save worker state under Worker.Status.State (gardener-attic/gardener-extensions#600, @vlvasilev)
  • Add Worker.Status.State restoration functionality
  • Add migration functionality
• [OPERATOR] The machine.sapcloud.io CRDs applied by the ./pkg/controller/worker package do now get a protection label for accidental deletion. See also: gardener/gardener#2066 (gardener-attic/gardener-extensions#625, @rfranzke)

[terraformer]

Action Required

• [OPERATOR] The Terraformer does now lookup the relevant data stored in ConfigMaps or Secrets live from the system instead of relying on mounted volumes. This is a breaking change as the volume mount approach does no longer work, please adapt your manifests according to the examples. The rationale behind it is to not rely on potentially stale kubelet cache while it mounts the volume which may, in rare cases, cause state loss. (gardener/terraformer#37, @rfranzke)

Improvements

• [OPERATOR] nsxt and random providers are now removed from the terraform bundle. (gardener/terraformer#38, @ialidzhikov)
• [OPERATOR] terraformer does no longer ignore the termination signals sent to PID 1. It does now send a termination signal to the terraform process itself and waits for its completion. This should prevent rare cases in which the terraformer was not storing the state of created infrastructure resources. (gardener/terraformer#36, @ialidzhikov)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.8.0
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.8.0

v1.7.0

[gardener-extension-provider-alicloud]

Action Required

• [OPERATOR] ⚠️ This version is not compatible with Gardener < v1.2. (#36, @georgekuruvillak)
  • The controlplanebackup webhook is removed as of gardener/gardener#1762. The controlplaneexposure webhook that was previously targeting StatefulSets is now targeting Etcd resources of the druid.

Improvements

• [USER] Metric server can now fetch node metrics in Alicloud now. (#43, @minchaow)
• [USER] The Infrastructure deletion does now succeed in case it never created anything but the cloud provider secret does not contain the correct credentials. (#41, @rfranzke)
• [USER] The Worker deletion does now succeed in case the cloud provider credentials were changed. (#41, @rfranzke)
• [USER] Do not mutate kube-apiserver exposure resources which Gardener marks as managed by it with core.gardener.cloud/apiserver-exposure: gardener-managed label. (#29, @mvladev)
• [OPERATOR] The Alicloud provider now allows Gardener to restart the Cloud-Controller-Manager and the Machine-Controller-Manager (see gardener/gardener#2098 for more information). (#59, @timuthy)
• [OPERATOR] provider-alicloud Shoot mutator is now able to properly handle .spec.healthCheckNodePort of vpn-shoot and addons-nginx-ingress-controller Services. (#50, @ialidzhikov)
• [OPERATOR] The gardener-extension-provider-alicloud now offers a validating webhook which checks shoot resources of type alicloud in the core.gardener.cloud group. Operators should register this webhook in the Garden cluster to further prevent invalid modifications on alicloud shoots. (#49, @minchaow)
• [DEVELOPER] Fix nil pointer when applying machine class chart (#42, @mvladev)

[gardener-extensions]

Improvements

• [USER] An issue in the machine reconciliation has been fixed that caused the reconciliation being stuck in some cases where a previously broken worker configuration (e.g., due to the specification of machine types that are not available in certain availability zones) has been corrected. (gardener-attic/gardener-extensions#626, @rfranzke)
• [USER] Allow force deletion of machines incase of cluster hibernation (gardener-attic/gardener-extensions#609, @prashanth26)
• [OPERATOR] An issue causing running terraformer container to leak on the Node without associated Pod resource is now fixed. This will prevent multiple containers to execute apply/destroy commands simultaneously in some cases (especially for long running terraformer Pods). (gardener-attic/gardener-extensions#605, @ialidzhikov)
• [OPERATOR] Credentials used by machine-controller-manager are now updated during worker deletion. (gardener-attic/gardener-extensions#606, @EmoinLanyu)

[machine-controller-manager]

Most notable changes

• [OPERATOR] Prepend mcm to all work queue metrics (gardener/machine-controller-manager#420, @prashanth26)
• [OPERATOR] Subsystems and Namespaces to MCM metrics (gardener/machine-controller-manager#420, @prashanth26)
• [OPERATOR] Renamed mcm_machine_deployment_items_total & mcm_machine_set_items_total metrics (gardener/machine-controller-manager#420, @prashanth26)
• [OPERATOR] Bugfix: Set deleteOnTermination to true by default for volumes. Disks that are created with the instance are deleted with instance termination. (gardener/machine-controller-manager#420, @prashanth26)

Improvements

• [USER] Azure: Support for accelerated networking enabled VMs (gardener/machine-controller-manager#438, @dkistner)
• [OPERATOR] Azure: VMs now can be created with image ID. (gardener/machine-controller-manager#436, @vpnachev)
• [OPERATOR] Improves the machine-creation and machine-deletion flow by listing and verifying the state of the machines before actual creation and deletion. (gardener/machine-controller-manager#432, @hardikdr)
• [OPERATOR] MCM now dynamically maps the node-objects with machines if Status.Node is not set. (gardener/machine-controller-manager#432, @hardikdr)
• [OPERATOR] Sort active machines by creation timestamp (gardener/machine-controller-manager#429, @prashanth26)
• [OPERATOR] Openstack: When a Server creation ERRORs, provide formatted Fault information (gardener/machine-controller-manager#427, @zuzzas)
• [OPERATOR] Set deleteOnTermination flag to true while deleting the VMs in AWS. (gardener/machine-controller-manager#420, @prashanth26)
• [OPERATOR] Skip eviction during drain if ForceDeletePods is enabled. (gardener/machine-controller-manager#416, @amshuman-kr)
• [OPERATOR] Openstack: Print API request/response debug when verbosity is set to 6 (gardener/machine-controller-manager#412, @kayrus)
• [OPERATOR] Azure: VM deletion checks any orphan dependant resources and tries to delete them if exists. (gardener/machine-controller-manager#406, @dkistner)
• [DEVELOPER] Azure: Update of the Azure SDK to use more recent version (gardener/machine-controller-manager#406, @dkistner)

[terraformer]

Improvements

• [OPERATOR] Update Terraform azurerm provider to support Azure NatGateway. (gardener/terraformer#35, @dkistner)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.7.0
gardener-extension-validator-alicloud: eu.gcr.io/gardener-project/gardener/extensions/validator-alicloud:v1.7.0

v1.6.1

no release notes available

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.6.1

v1.6.0

[gardener-extension-provider-alicloud]

Improvements

• [OPERATOR] gardener-extension-provider-alicloud does now allow Alicloud csi-controller to access the Alicloud APIs. (#33, @ialidzhikov)

Docker Images

gardener-extension-provider-alicloud: eu.gcr.io/gardener-project/gardener/extensions/provider-alicloud:v1.6.0