Skip to content
This repository has been archived by the owner on Apr 7, 2020. It is now read-only.

1.0.0
Compare
Choose a tag to compare
@gardener-robot-ci-2 gardener-robot-ci-2 released this 18 Nov 12:24
1.0.0
5b9d35d

[gardener-extensions]

Action Required

  • [USER] If a VPC is to be re-used for shoot clusters, a (manually pre-provisioned) GCP Cloud Router name needs to be specified as well, this is to avoid hitting quota limits (5 Cloud routers / VPC) and allowing all the Cloud NATs to share that Cloud Router. If no Cloud Router name is specified, all the nodes will be assigned a public IP. (#417, @zanetworker)
  • [USER] After two months, no public IPs will be allowed and specifying a Cloud Router name will be enforced. Please adapt your shoot deployments into a existing VPCs as soon as possible. (#417, @zanetworker)
  • [OPERATOR] Since version 0.13.0 the fields publisher, offer, sku and version in the AzureMachineClass are deprecated and now support for them has been removed. Please switch your Azure provider extension to use URN as OS image reference, which is the replacement of the deprecated fields. (#421, @vpnachev)
  • [OPERATOR] All extensions controller do no longer understand the deprecated garden.sapcloud.io/v1beta1 API group. Please use at least Gardener 0.31.0. (#392, @rfranzke)
  • [OPERATOR] If you want to keep using cloud-init for SuSE-JeOS nodes bootstrapping, use osConfig.format and osConfig.bootCmd values to switch to cloud-init. Sample values can be found here. (#297, @pablochacin)
  • [DEVELOPER] pkg/terraformer package has renamed and deleted funcs. If you are vendoring this package in your project, make sure to adapt to these changes when adopting the new version of gardener/gardener-extensions. (#426, @ialidzhikov)

Most notable changes

  • [USER] The AWS infrastructure controller no longer creates the security group for bastions. Also, for existing clusters, it removes this rule now. (#431, @ThormaehlenFred)
  • [DEVELOPER] The terraformer package was moved from gardener/gardener to gardener/gardener-extensions/pkg/terraformer. (#418, @tim-ebert)

Improvements

  • [USER] Calico Typha can be disabled for shoot clusters via Shoot.spec.networking.providerConfig.typha.enabled=false. Please read the docs before to consider to disable typha. (#432, @vpnachev)
  • [USER] An issue that prevented the control plane deployment for AWS shoots that don't specify a controlPlaneConfig in the Shoot specification has been resolved. (#403, @rfranzke)
  • [USER] The os volume type configuration for worker machines of Azure Shoot cluster will be now passed correctly, but only if the selected volume type is a valid Azure volume type. (#401, @dkistner)
    • This will trigger a rolling update of all machines in the cluster during the maintenance window, if configured.
  • [USER] An issue that prevented GCP shoot worker nodes from getting external IP addresses has been fixed. (#398, @zanetworker)
  • [USER] The recent changes for the GCP controller regarding usage of cloud NAT have been reverted due to instabilities. (09e8023)
  • [OPERATOR] pkg/terraformer package does now use a Pod for terraform apply/destroy operations. The motivation for this changes is to prevent multiple Pods to execute apply/destroy commands simultaneously in some cases. (#426, @ialidzhikov)
  • [OPERATOR] pkg/terraformer package does no longer deploy a Terraformer validation pod. It executes directly terraform apply/destroy. (#426, @ialidzhikov)
  • [OPERATOR] terraformer does now delete job and pods only in its namespace. This fixes an issue that prevents simultaneous creation of Shoots with the same name (but different projects) on the same Seed. (#425, @ialidzhikov)
  • [OPERATOR] Make the env vars OS_CONFIG_FORMAT and BOOT_COMMAND optional to allow the hyper binary to run without them. (#423, @vpnachev)
  • [OPERATOR] MCM has new role for create, delete and list secrets in shoot's kube-system namespace (#422, @vlvasilev)
  • [OPERATOR] OpenStack: rename the default storage class from "default-class" to "default" (#415, @kayrus)
  • [OPERATOR] Ensure required packages are installed in JeOS (#400, @kayrus)
  • [OPERATOR] Allows deployment of JeOS-based worker nodes on cloud providers on which cloud-init is not supported. By default bash script bootstrapping is used. (#297, @pablochacin)
  • [DEVELOPER] The default storage class annotations are now overwritten to the desired values using the forceOverwriteAnnotation parameter in the extension-controlplane-storageclasses managed resource. (#436, @zanetworker)
  • [DEVELOPER] Developers who write and register actuators with Gardener-Extension means must now pass the extension type they want to act upon. This makes sure that reconciliation is only triggered for desired types. (#414, @timuthy)
  • [DEVELOPER] sigs.k8s.io/controller-runtime is updated to v0.2.0-beta.5. (#413, @ialidzhikov)

[cert-management]

Improvements

[external-dns-management]

Improvements

  • [USER] For openstack designate it is possible now to (gardener/external-dns-management#43, @mandelsoft)
    • specify a CA certificate in the credentails. The key is CACERT.
    • Additionally a dedicated client certificate and key can used
    • for the https requests (CLIENTCERT/CLIENTKEY)

[machine-controller-manager]

Action Required

  • [USER] Since version 0.22.0 the fields Spec.Properties.StorageProfile.ImageReference.[Publisher|Offer|Sku|Version] in the AzureMachineClass have been deprecated and now they are completely removed. Please switch to Spec.Properties.StorageProfile.ImageReference.URN` before upgrading to this version or higher. (gardener/machine-controller-manager#353, @vpnachev)

Improvements

Docker Images

gardener-extension-hyper: eu.gcr.io/gardener-project/gardener/gardener-extension-hyper:1.0.0

Assets 3
Loading