Skip to content

Releases: gardener/gardener-extension-provider-vsphere

v0.16.0

11 Jul 19:49
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

🏃 Others

[machine-controller-manager-provider-vsphere]

🏃 Others

v0.14.1

30 Jun 22:52
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

🏃 Others

v0.14.0

30 Jun 20:21
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

✨ New Features

🏃 Others

[machine-controller-manager]

📖 Documentation

🏃 Others

[machine-controller-manager-provider-vsphere]

🏃 Others

📰 Noteworthy

v0.13.0

09 May 18:21
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

⚠️ Breaking Changes

✨ New Features

🐛 Bug Fixes

📖 Documentation

🏃 Others

[machine-controller-manager]

🐛 Bug Fixes

🏃 Others

[machine-controller-manager-provider-vsphere]

🐛 Bug Fixes

🏃 Others

v0.12.1

03 Feb 12:25
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

🏃 Others

v0.12.0

31 Jan 08:11
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

⚠️ Breaking Changes

  • [OPERATOR] The default leader election resource lock of gardener-extension-provider-vsphere has been changed from configmapsleases to leases. (gardener/gardener-extension-provider-vsphere#194, @acumino)
    • Please make sure, that you had at least [email protected] running before upgrading to v0.12.0, so that it has successfully acquired leadership with the hybrid resource lock (configmapsleases) at least once.

✨ New Features

🏃 Others

📰 Noteworthy

[machine-controller-manager]

⚠️ Breaking Changes

  • [OPERATOR] Components that deploy the machine-controller-manager will now have to adapt the RBAC rules to allow machine-controller-manager to maintain its leader election resource lock in leases as well. (gardener/machine-controller-manager#662, @acumino)

✨ New Features

🐛 Bug Fixes

  • [OPERATOR] A bug has been fixed in the pre-delivered CRD manifests for MCM (/kubernetes/crds). It caused data to be pruned from MCM related resources and led to reconciliation issues. (gardener/machine-controller-manager#641, @timuthy)

📖 Documentation

🏃 Others

[machine-controller-manager-provider-vsphere]

🏃 Others

📰 Noteworthy

v0.11.0

15 Sep 10:14
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

✨ New Features

  • [USER] The vSphere extension does now support shoot clusters with Kubernetes version 1.22. You should consider the Kubernetes release notes before upgrading to 1.22. (#170, @timuthy)

🐛 Bug Fixes

  • [USER] Do not trigger a node rollout when switching from CRI.Name==nil to CRI.Name==docker. (#167, @BeckerMax)
  • [OPERATOR] using patched vsphere-csi-driver v2.3.0-gardener1 to fix volume attachment issue on hibernation (#174, @MartinWeindel)

🏃 Others

  • [OPERATOR] Update vSphere cloud provider to v1.22 (patched version) (#173, @MartinWeindel)
  • [OPERATOR] Update vsphere-csi-driver to v2.3.0 (#173, @MartinWeindel)
  • [OPERATOR] The metrics-server is now properly able to communicate with the kubelets in order to expose metrics about nodes and pods. (#171, @MartinWeindel)
  • [OPERATOR] machine-controller-manager logs are exposed to the end-users (#168, @vlvasilev)

[machine-controller-manager]

⚠️ Breaking Changes

  • [OPERATOR] Draining of pods with PVs (Persistent Volume) now waits for re-attachment of PV on a different node when volumeAttachments support is enabled on the cluster. Else it falls back to the default PV reattachment timeout value configured. The default value is 90s and this can be overwritten via the machine-pv-reattach-timeout flag. Please enable permissions to allow listing of volumeAttachments resource while importing these changes. (gardener/machine-controller-manager#608, @prashanth26)

✨ New Features

🐛 Bug Fixes

🏃 Others

v0.10.0

21 Jun 08:48
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

✨ New Features

  • [OPERATOR] The existing ValidatingWebhookConfiguration of admission-vsphere for Shoot validation does now validate also the Shoot secret. admission-vsphere does now feature also a new webhook that prevents Shoot secret to be updated with invalid keys. (#153, @vpnachev)

🏃 Others

  • [USER] The following image is updated (see CHANGELOG for more details): (#157, @MartinWeindel)
    • k8s.gcr.io/sig-storage/livenessprobe: v2.2.0 -> v2.3.0
  • [OPERATOR] update of vsphere-csi driver to release v2.2.1 (#162, @MartinWeindel)
  • [OPERATOR] When creating or updating shoots, any Kubernetes feature gates mentioned are validated against the Kubernetes version. If any feature gates are unknown or not supported in the Kubernetes version, the validation fails. (#161, @stoyanr)

[machine-controller-manager]

✨ New Features

🐛 Bug Fixes

[machine-controller-manager-provider-vsphere]

🏃 Others

v0.9.0

11 May 15:14
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

⚠️ Breaking Changes

  • [OPERATOR] The garden cluster identity is now used instead of the obsolete garden.identity. (#151, @MartinWeindel)
    • Please note: If you have already used this extension in version <= v0.8.0, you need need to manually change the tags of scope cluster and owner of any NSX-T load balancer resources created by the cloud-controller-manager (project cloud-provider-vsphere). These are "load balancers", "virtual servers", "server pools", and "monitors".

v0.8.0

05 May 13:11
Compare
Choose a tag to compare

[gardener-extension-provider-vsphere]

🐛 Bug Fixes

  • [USER] The following image is updated (see CHANGELOG for more details): (#149, @ialidzhikov)
    • k8s.gcr.io/sig-storage/livenessprobe: v2.1.0 -> v2.2.0
  • [OPERATOR] An issue causing decoding of a Shoot resource to fail because of strict decoding is now fixed. (#147, @ialidzhikov)