Skip to content

Releases: gardener/gardener-extension-provider-openstack

v1.7.0

26 May 16:36
Compare
Choose a tag to compare

[gardener-extension-provider-openstack]

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. (#82, @rfranzke)
  • [OPERATOR] added optional domain field to floatingpools in the cloud profile constraints (#76, @MartinWeindel)
  • [OPERATOR] If a floating pool in the cloud profile defines no load balancer class named "default", the first one is used as default. (#74, @MartinWeindel)
  • [OPERATOR] The pre-defined ValidatingWebhookConfiguration assets now set sideEffects=None. This enables dry-run related operations, like kubectl diff, for core.gardener.cloud resources. (#70, @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

Docker Images

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

v1.6.1

12 May 10:43
Compare
Choose a tag to compare

[gardener]

Improvements

Docker Images

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

v1.6.0

07 May 06:33
Compare
Choose a tag to compare

[gardener-extension-provider-openstack]

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. (#68, @ialidzhikov)
  • [OPERATOR] The useOctavia setting of the cloud-controller-manager is now explicitly set to false. You can set it to true using the ControlPlaneConfig. (#66, @rfranzke)
  • [OPERATOR] implement Migrate and Restore functionality (#53, @vlvasilev)

[gardener]

Improvements

Docker Images

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

v1.5.1

20 Apr 14:32
Compare
Choose a tag to compare

[gardener-extension-provider-openstack]

Improvements

  • [OPERATOR] The useOctavia setting of the cloud-controller-manager is now explicitly set to false. You can set it to true using the ControlPlaneConfig. (1a1683f)

Docker Images

gardener-extension-provider-openstack: eu.gcr.io/gardener-project/gardener/extensions/provider-openstack:v1.5.1
gardener-extension-validator-openstack: eu.gcr.io/gardener-project/gardener/extensions/validator-openstack:v1.5.1

v1.5.0

16 Apr 15:28
Compare
Choose a tag to compare

[gardener-extension-provider-openstack]

Most notable changes

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

Improvements

[gardener-extensions]

Improvements

[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-openstack: eu.gcr.io/gardener-project/gardener/extensions/provider-openstack:v1.5.0
gardener-extension-validator-openstack: eu.gcr.io/gardener-project/gardener/extensions/validator-openstack:v1.5.0

v1.4.0

02 Apr 05:44
Compare
Choose a tag to compare

[gardener-extension-provider-openstack]

Action Required

  • [OPERATOR] ⚠️ This version is not compatible with Gardener < v1.2. (#37, @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.

Most notable changes

  • [USER] The OpenStack extension does now support shoot clusters with Kubernetes version 1.18. You should consider the Kubernetes release notes before upgrading to 1.18. (#54, @timuthy)
  • [OPERATOR] It is now possible to configure useOctavia=true in the CloudProfileConfig in case the underlying OpenStack system uses Octavia for network load balancing. (#38, @rfranzke)
  • [OPERATOR] The gardener-extension-provider-openstack now offers a validating webhook which checks shoot resources of type openstack in the core.gardener.cloud group. Operators should register this webhook in the Garden cluster to further prevent invalid modifications on openstack shoots. (#36, @timuthy)

Improvements

  • [USER] The Infrastructure deletion does now succeed in case it never created anything but the cloud provider secret does not contain the correct credentials. (#42, @rfranzke)
  • [USER] The Worker deletion does now succeed in case the cloud provider credentials were changed. (#42, @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. (#33, @mvladev)
  • [OPERATOR] The OpenStack provider now allows Gardener to restart the Cloud-Controller-Manager and the Machine-Controller-Manager (see gardener/gardener#2098 for more information). (#54, @timuthy)
  • [OPERATOR] Use validationContext consistently during validation (#47, @zanetworker)
  • [OPERATOR] The OpenStack shoot validator now checks that workers[].minimum != 0 if workers[].maximum >0 since autoscaling does not support this setup yet. (#44, @timuthy)
  • [OPERATOR] The OpenStack extension does now by default mount the host certificates from /etc/ssl and /usr/share/ca-certificates into the pods that are running in the seed and need to interact with the OpenStack API (kube-apiserver, kube-controller-manager (only until #1 is fixed), and cloud-controller-manager). (#39, @rfranzke)
    • This is to accommodate OpenStack environments that are serving certificates signed by CAs not commonly known/trusted.
  • [DEVELOPER] Fix nil pointer when applying machine class chart (#43, @mvladev)

[gardener-extensions]

Improvements

[machine-controller-manager]

Most notable changes

Improvements

[terraformer]

Improvements

Docker Images

gardener-extension-provider-openstack: eu.gcr.io/gardener-project/gardener/extensions/provider-openstack:v1.4.0
gardener-extension-validator-openstack: eu.gcr.io/gardener-project/gardener/extensions/validator-openstack:v1.4.0

v1.3.0

06 Feb 11:48
Compare
Choose a tag to compare

[gardener-extension-provider-openstack]

Improvements

[machine-controller-manager]

Most notable changes

Improvements

[terraformer]

Most notable changes

Improvements

Docker Images

gardener-extension-provider-openstack: eu.gcr.io/gardener-project/gardener/extensions/provider-openstack:v1.3.0