Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, and OnMetal with minimal TCO.
OTHER License
Published by gardener-robot-ci-1 over 5 years ago
node-exporter
deployed by Gardener in kube-system
now runs on port 16909
. Adjust your Prometheus configuration, if it uses the old 9100
port. (#970, @mvladev)1.11.x
. Before updating to this Gardener version you will have to update seed cluster to at least Kubernetes version 1.11.x
. (#937, @swapnilgm)node-exporter
deployed in kube-system
now runs on port 16909
. (#970, @mvladev)labels
, annotations
, and taints
for each worker pool in the Shoot
manifest. Please consult the example Shoot manifests for more information on how to configure it. (#952, @rfranzke)StatefulSet
will now use gardener.cloud-fast
storage class which will be configured to have fast cloud provider disks with more IOPS. The size of PV attached to etcd-main pods will differ per cloud provider. (#937, @swapnilgm)
cluster-autoscaler.kubernetes.io/safe-to-evict=false
, hence, seed nodes on which etcd is scheduled will be refrained for removal by cluster autoscale in case of scale down. (#937, @swapnilgm)Nodes
in the Shoot cluster after ending hibernation. (#1015, @timuthy)PayByTraffic
policy for new clusters to save costs. (#994, @jia-jerry)CustomResources
and APIServices
during the deletion of a Shoot cluster before further resources get deleted. (#989, @timuthy)vpa-exporter
into seeds. (#982, @wyb1)Plant
health check has been fixed. (#973, @danielfoehrKn)warning
level alerts (#954, @wyb1)CrashLoopBackoff
. (gardener/dependency-watchdog#0, @georgekuruvillak)embedded-etcd-quota-bytes
flag to allow configuring the backend quota size of the embedded etcd instance used during restoration of data. (gardener/etcd-backup-restore#134, @shreyas-s-rao)v1.12.0
. (gardener/etcd-backup-restore#132, @ialidzhikov)9570
(gardener/vpa-exporter#5, @wyb1)--port
flag to specify on which port prometheus metrics should be exposed. (gardener/vpa-exporter#3, @wyb1)targetName
and targetKind
labels (gardener/vpa-exporter#6, @wyb1)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.22.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.22.0
Published by gardener-robot-ci-1 over 5 years ago
CustomResources
and APIServices
during the deletion of a Shoot cluster before further resources get deleted. (f05695ad9f17174a276a3a12901eafc3fed6e0e4)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.21.2
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.21.2
Published by gardener-robot-ci-1 over 5 years ago
node-exporter
deployed by Gardener in kube-system
now runs on port 16909
. Adjust your Prometheus configuration, if it uses the old 9100
port. (06bdbab1a7c3018916a12e4abe73f78a3fb8d8c8)node-exporter
deployed in kube-system
now runs on port 16909
. (06bdbab1a7c3018916a12e4abe73f78a3fb8d8c8)Plant
health check has been fixed. (f795cf99f13efacc542767361cf572922ab0e607)warning
level alerts (fab92f41149efd1ceb9e739d9e8c1b2cd8b1bf42)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.21.1
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.21.1
Published by gardener-robot-ci-1 over 5 years ago
.spec.addons.kubenetes-dashboard.authenticationMode={basic,token}
(defaults to basic
). (#941, @rfranzke)garden.sapcloud.io/role=seed
(#944, @vpnachev)ShootSeedManager
admission plugin is now configurable by providing an AdmissionConfiguration file to the API server. This admission plugin is responsible for automatically determining an appropriate seed for a created shoot. It does now support two strategies: SameRegion
(default) which will only consider seeds of the same provider and in the same region like the shoot, or MinimalDistance
which will first try to find a seed of the same provider and in the same region, but if no such seed can be found it will choose the geographically nearest seed cluster. (#917, @danielfoehrKn)VPA
feature gate then the VPA mode for all Prometheus instances in the seed will now be set to Auto
mode. That means that the pod's resource requests will change based on the recommendations of the VPA. If Prometheus is using too much/too little resources it will be killed by the VPA and given new resource requests (can only happen to pods that are 12h+ old or get killed through other means). (#915, @wyb1)shoot.garden.sapcloud.io/ignore-alerts
to true
if they want don't want alerts to fire for their shoot cluster. (#957, @wyb1)seed.gardener.cloud/provider={aws,azure,...}
and shoot.gardener.cloud/provider={aws,azure,...}
. (#949, @rfranzke)Role
in the respective namespace instead of relying on a ClusterRole
that was deployed during seed bootstrap process. (#949, @rfranzke)grafana/grafana
: 6.0.1
-> 6.1.4
docker.elastic.co/elasticsearch/elasticsearch-oss
: 6.5.4
-> 6.7.1
docker.elastic.co/kibana/kibana-oss
: 6.5.4
-> 6.7.1
fluent/fluent-bit
: 1.0.5
-> 1.0.6
Off
mode. (#926, @wyb1)unmanaged
DNS provider and does not deploy DNS records for it. (#922, @vpnachev)validate-namespace-deletion
is now called only for Project namespaces. (#908, @mvladev)garden.sapcloud.io:admin
cluster role does now allow reading namespaces. (#907, @petersutter)v1.12.0
. (gardener/machine-controller-manager#237, @ialidzhikov)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.21.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.21.0
Published by gardener-robot-ci-1 over 5 years ago
ApiServerNotReachable
alerts has been fixed. (#909, @wyb1)garden.sapcloud.io:admin
cluster role does now allow reading namespaces. (23f717e6b933cd20d0e66d98ca1a91b13064827c)validate-namespace-deletion
is now called only for Project namespaces. (3ed4a1240625c48e22b854355385398531151b7f)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.20.2
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.20.2
Published by gardener-robot-ci-1 over 5 years ago
1.14.x
but continues to support Kubernetes 1.13.x
. (d67cc224cd9985a0c5cd19f915ef850253e32ab7)Plant
test has been fixed. (61243faf6df7a0c1e8383406f8afb12ef70e0d54)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.20.1
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.20.1
Published by gardener-robot-ci-1 over 5 years ago
aws-route53
, google-clouddns
, etc. (see GEP-1 on extensibility). We have prepared the implementation of the external-dns-management which supports AWS Route53, Alicloud DNS, Azure DNS, Google CloudDNS, and OpenStack Designate. After updating Gardener you need to create corresponding ControllerRegistration
resources to make these extension controllers known to Gardener (otherwise none of your shoots will be able to get reconciled anymore). Please find example ControllerRegistration
resources here. To get information about more details please walk through these documents. (#850, @rfranzke)Secret
example files. Also be aware of the fact that the Gardener Helm chart changed! (#850, @rfranzke)shoot.garden.sapcloud.io/ignore
annotation. (#878, @ialidzhikov)
shoot.garden.sapcloud.io/ignore
annotation but any other value than ("1", "t", "T", "true", "TRUE", "True") will be considered for reconciliation.location
(timezone) for your hibernation schedules in the Shoot
resource. (#876, @adracus).spec.kubernetes.kubelet.podPidsLimit
flag in the Shoot
specification. (#853, @rfranzke).spec.dns.hostedZoneID
field in the Shoot
resource is deprecated and no longer respected/used. It will be removed in the future. (#850, @rfranzke)nginx-ingress
addon for shoot clusters is now deprecated (but still supported for a couple of releases). Shoot owners are now encouraged to deploy an Ingress
controller according to their preferences themselves. (#837, @timuthy)Plant
resource. Gardener will do basic health checks of the cluster, and it allows you to manage all your clusters (managed by Gardener or any other tool) at a single place. (#826, @zanetworker).spec.dns.provider=nil
. (6b542463ad0424a0ba04c3998c47107d1003ae51)dns.garden.sapcloud.io/domain
, dns.garden.sapcloud.io/hostedZoneID
, and dns.garden.sapcloud.io/provider
annotations for domain secrets are deprecated and will be removed in a future version. Please use dns.gardener.cloud/domain
and dns.gardener.cloud/provider
now. (#850, @rfranzke)Initializer
feature is entirely dropped with Kubernetes 1.14 Gardener does now no longer rely on it. It was used to enable the cloud-controller-manager for labelling created PVs. This is now done by the PersistentVolumeLabel
admission controller inside the kube-apiserver. Consequently, the kube-apiserver does now have information about the cloud (credentials/config). (#838, @rfranzke)kube-dashboard
and blackbox-exporter
to start if .spec.kubernetes.allowPrivilegedContainers
was set to false
(securityContext
was missing). (#883, @mvladev)HorizontalPodAutoscaler
for CoreDNS
has been changed to 2. (ee25f9ca2cb6f3e7a3035fce5fb6f96ee600cae0)0.5.0
(#898, @wyb1)HorizontalPodAutoscaler
for kube-apiserver
now scales based on memory metrics (in addition to the existing CPU metrics). (#890, @amshuman-kr)fluent-bit
has been upgraded from 1.0.4
to 1.0.5
. (#860, @ialidzhikov)kube-proxy
and node-exporter
have been doubled. (#828, @ggaurav10)http_auth
option for basic auth against elasticsearch. (gardener/logging#24, @ialidzhikov)v1.12.0
. (gardener/logging#23, @ialidzhikov)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.20.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.20.0
Published by gardener-robot-ci-1 over 5 years ago
kube-proxy
and node-exporter
have been doubled. (575f7a7b3cda85e16c90dd4bd5b9c91d4ea591a6)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.18.2
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.18.2
Published by gardener-robot-ci-1 over 5 years ago
ControllerRegistration
controller has been fixed. (#832, @rfranzke)kube-proxy
and node-exporter
have been doubled. (6aee4973f0133a50469a658c60d4bb62e6d140c6)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.19.1
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.19.1
Published by gardener-robot-ci-1 over 5 years ago
gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.18.1
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.18.1
embedded-etcd-quota-bytes
flag to allow configuring the backend quota size of the embedded etcd instance used during restoration of data. (gardener/etcd-backup-restore#136, @swapnilgm)IPVS
mode in kube-proxy
can now be enabled via the Shoot's spec.kubernetes.kubeProxy.mode
field. Recommended versions of Kubernetes which can be used with this configuration are: (#496, @mvladev)
~1.11.6
~1.12.4
~1.13.1
^1.14
gardener-controller-manager
now uses a cached discovery client for the Garden
cluster that can be configured via entries in the ControllerManagerConfiguration
. Also, the previous two environment variables KUBECONFIG
and GARDENER_KUBECONFIG
have been merged into a single KUBECONFIG
variable. This means Gardener will communicate to only a single Garden
cluster, being more in line with other Kubernetes controllers. (#778, @adracus)VPA
feature gate is enabled then Gardener will deploy the Vertical Pod Autoscaler into the garden
namespace of every seed cluster. (#739, @wyb1)VPA
feature gate is enabled then the vertical pod autoscaler will provide scaling recommendations for the central Prometheus in the garden
namespace as well as all shoot-specific Prometheus instances. It will not yet scale them automatically. We might enable this in a future release. (#739, @wyb1)Shoot
's control plane condition indicating issues during a rolling worker upgrade due to a purposefully missing cluster-autoscaler has been fixed. (#787, @adracus)initContainers
. (#798, @deitch)v1.12.0
. (#790, @ialidzhikov)3.8
. (gardener/vpn#38, @marwinski)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.19.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.19.0
[OPERATOR] ⚠️ Gardener does now require that all the registered seed clusters have at least Kubernetes version 1.11+
. You may only use a seed with Kubernetes version 1.10+
if you have enabled the CustomResourceSubresources
feature gate prior to upgrading Gardener. (d102d6d088490e5e59d88e4137ee954842be82ac)
[OPERATOR] ⚠️ Gardener does no longer have in-tree supported for operating system configurations. Instead, it now relies on extension controllers to generate this configuration for the specific OS they have been developed for (see GEP-1 on extensibility). We have prepared the implementation of the CoreOS Container Linux extension and the CoreOS Container Linux (Alicloud-specific) extension. After updating Gardener you need to create corresponding ControllerRegistration
resources to make these extension controllers known to Gardener (otherwise none of your shoots will be able to get reconciled anymore). Please find example ControllerRegistration
resources here and here. Please ensure that you use the extension controllers of at least version 0.4.0
. To get information about more details please walk through these documents. (#713, @rfranzke)
[OPERATOR] ⚠️ This release requires manual migration steps as it incorporates the latest version (0.14.0) of the machine-controller-manager. In this version MCM has incompatibly changed to use CRD subresources. Also, now that you will register extension controllers for the CoreOS Container Linux operating system you must update the machine image name in the CloudProfile
s for Alicloud to coreos-alicloud
, and for all other providers (AWS, GCP, ...) to coreos
. Gardener will try to update the specification of all existing Shoot
objects when starting, so make sure that you update the CloudProfile
s (otherwise, the update request by Gardener will not happen and shoots may break). Please follow the following steps:
kubectl -n garden scale deployment/gardener-controller-manager --replicas=0
for ns in $(kubectl get namespaces -l garden.sapcloud.io/role=shoot -o jsonpath={.items..metadata.name}); do kubectl -n ${ns} scale deployment/machine-controller-manager --replicas=0 && echo "Scaled down machine-controller-manager in shoot namespace ${ns}"; done
kubectl get pod --all-namespaces | grep machine-controller-manager
(should return no results)kubectl apply -f https://raw.githubusercontent.com/gardener/gardener/0.18.0/charts/seed-bootstrap/templates/crd-machines.yaml
for ns in $(kubectl get namespaces -l garden.sapcloud.io/role=shoot -o jsonpath={.items..metadata.name}); do kubectl -n ${ns} set image deployment/machine-controller-manager machine-controller-manager=eu.gcr.io/gardener-project/gardener/machine-controller-manager:0.14.0 && echo "Updated machine-controller-manager in shoot namespace ${ns}"; done
for ns in $(kubectl get namespaces -l garden.sapcloud.io/role=shoot -o jsonpath={.items..metadata.name}); do kubectl -n ${ns} scale deployment/machine-controller-manager --replicas=1 && echo "Scaled up machine-controller-manager in shoot namespace ${ns}"; done
CloudProfile
resources in the garden cluster as described above.kubectl -n garden scale deployment/gardener-controller-manager --replicas=1
ControllerRegistration
resources as described above: kubectl apply -f https://raw.githubusercontent.com/gardener/gardener-extensions/0.4.0/controllers/os-coreos/example/controller-registration.yaml
(and, for Alicloud, kubectl apply -f https://raw.githubusercontent.com/gardener/gardener-extensions/0.4.0/controllers/os-coreos-alicloud/example/controller-registration.yaml
)⚠️ Please note that, after we have now removed in-tree support for operating systems, the generated user-data used for bootstrapping VMs does syntactically change. This will trigger a rolling update of all worker VMs for all existing shoots as soon as Gardener reconciles them. (#713, #774, @rfranzke)
[OPERATOR] Developers need to run make dev-setup-extensions
to prepare their local Gardener development setup. They should also update the machine image name in the CloudProfile
s for Alicloud to coreos-alicloud
, and for all other providers to coreos
. (#713, @rfranzke)
Service
object of type LoadBalancer
with cloud.google.com/load-balancer-type=Internal
. (#765, @DockToFuture)etcd
has been upgraded from 3.3.10
to 3.3.12
. (#748, @swapnilgm)0.21.0
to 0.22.0
. Please note that there were breaking changes, check out the release notes. (e360f3d7a7fdfa6d415c4c073c11d4faf6e4a075)hyperkube
/kubectl
. (e2ab6b81754af2dbd13565ebb9aac4193ae9b18e)status=False
are 'pardoned' to status=Progressing
if no error has occurred yet. (#776, @adracus)CoreDNS
produced by the blackbox-exporter
running in the shoot cluster's kube-system
is now reduced (#749, @zanetworker)kube2iam
have been increased. (6681717a9ed3d9b60e82f389bf01405ae862eeb6)FELIX_LOGSEVERITYSCREEN
level has been set to error
. (43af59a6ba3b8b93068752d1485a186cdff27d76)fluent-bit
has been upgraded from 1.0.3
to 1.0.4
. (#763, @ialidzhikov)v0.4.1
to v0.6.0
. (#708, @timuthy)v2.7.1
. (#705, @wyb1)OutOfDisk
node conditions for 1.13 clusters. See https://github.com/kubernetes/kubernetes/pull/72507 for more details. (#691, @rfranzke)v8.8
to v9.0
. (57b4326ea577f8fedaf43182a81b40ccc2351511)etcd
statefulset is now automatically rolled in case the backup secret changes. (2ce71537cb42355cc2310307b9d90b9257c195d0)minimumVolumeSize=20Gi
. (3e4406f1f3efacdd95c8b1eca9b4479d87c4ab8a)tolerations
section in the node-exporter manifest has been removed. (0fb3aefb6c0e433a4d65f8b1e7226fe219beedd1)MachineDeployment
object from Machine
object. (gardener/autoscaler#15, @hardikdr)aws-lb-readvertiser
does now ensure that the load balancer name provided via command line flags is a FQDN. If not, it will automatically convert it before starting the control loops. (gardener/aws-lb-readvertiser#12, @zanetworker)delta-snapshot-memory-limit
to restrict memory consumption due to periodic delta snapshots. (gardener/etcd-backup-restore#84, @swapnilgm)AllowReauth
flag for swift authentication call to true
. (gardener/etcd-backup-restore#80, @georgekuruvillak)0.11.6
to 0.11.11
. (gardener/terraformer#18, @rfranzke)1.17.0
to 1.60.0
. (gardener/terraformer#18, @rfranzke)1.4.0
to 1.22.1
. (gardener/terraformer#18, @rfranzke)1.12.0
to 1.20.0
. (gardener/terraformer#18, @rfranzke)1.4.0
to 1.16.0
. (gardener/terraformer#18, @rfranzke)1.22.0
to 1.31.0
. (gardener/terraformer#18, @rfranzke)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.18.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.18.0
MachineDeployment
object from Machine
object. (gardener/autoscaler#15, @hardikdr)aws-lb-readvertiser
does now ensure that the load balancer name provided via command line flags is a FQDN. If not, it will automatically convert it before starting the control loops. (gardener/aws-lb-readvertiser#12, @zanetworker)delta-snapshot-memory-limit
to restrict memory consumption due to periodic delta snapshots. (gardener/etcd-backup-restore#84, @swapnilgm)AllowReauth
flag for swift authentication call to true
. (gardener/etcd-backup-restore#80, @georgekuruvillak)0.21.0
to 0.22.0
. Please note that there were breaking changes, check out the release notes. (0c190c9a10a4f0f7216e7e4578a285483a625737)etcd
has been upgraded from 3.3.10
to 3.3.12
. (66d86cc9790f74d9b3bd37e57201e74da121ee44)kube2iam
have been increased. (debdb794c9225b4840ccc513dc9f088292212437)CoreDNS
produced by the blackbox-exporter
running in the shoot cluster's kube-system
is now reduced (4b676eb8c9f21042a75d5d2df62b2fd04e5b3c6e)v8.8
to v9.0
. (cb1b9d4e599ec2079f42ea14f73740ac2bf0dd37)etcd
statefulset is now automatically rolled in case the backup secret changes. (eeafbf129a755dcd6a71cf625605a2e111333061)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.17.4
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.17.4
gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.17.3
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.17.3
minimumVolumeSize=20Gi
. (#735, @jia-jerry)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.17.2
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.17.2
FELIX_LOGSEVERITYSCREEN
level has been set to error
. (22db1dd9cdde0dc8a6b1633500bc1daa2e66a15d)OutOfDisk
node conditions for 1.13 clusters. See https://github.com/kubernetes/kubernetes/pull/72507 for more details. (448be661e753f56d5adb768c57eefa55823abc4d)tolerations
section in the node-exporter manifest has been removed. (4b8d1a7b450bb33f4faf70aafdd1fc896a15fe1f)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.17.1
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.17.1
componentconfig/v1alpha1
API group has been renamed to controllermanager.config.gardener.cloud/v1alpha1
(developers need to update the API version in their local config file in the dev/
folder). (#650, @rfranzke)spec.cloud.seed
to Shoot
s so that end-users can query for all shoot clusters on a particular Seed, e.g. kubectl -n garden-my-project get shoot --field-selector .spec.cloud.seed=aws-eu1
. (#677, @mvladev).spec.backup
section in the Shoot
resource is deprecated and no longer evaluated. Instead, operators are now asked to provide a meaningful backup schedule in the Gardener configuration. (#666, @timuthy).spec.addons.monocular
field in the Shoot
resource was deprecated since long and is now no longer evaluated/respected at all, however, it is kept for API compatibility reasons. Users must deploy Monocular on their own if they want to use it. Rolling out this Gardener version will delete it from all existing shoot clusters that have had enabled it. (#658, @rfranzke)1.11.x
is supported by Gardener on Alicloud in this PR (#626, @jia-jerry)5m
grace period.PersistentVolume
resources in a shoot cluster are now deleted when the shoot itself is deleted (independent of the specified reclaimPolicy
). (b227e42f3c876dbc0afa7214f69b54d19e8a7e99).spec.backup
section in the Shoot
resource is deprecated and no longer evaluated. Instead, operators are now asked to provide a meaningful backup schedule in the gardener-controller-manager's configuration file which applies to all shoot clusters. If not specified the schedule will be defaulted to "once every 24 hours". (#666, @timuthy)
calico
and the node-exporter
have been switched to error
to reduce the number of noisy log messages. (#672, @DockToFuture)NoSchedule
, CriticalAddonsOnly
, and NoExecute
taints on nodes. (#657, @rfranzke)14d
. (#655, @ialidzhikov)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.17.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.17.0
1.13.1
of client-go
. (gardener/cert-broker#13, @timuthy)secrets
without a secret lister
. This improves the applications memory consumption. (gardener/cert-broker#12, @timuthy)delta-snapshot-memory-limit
to restrict memory consumption due to periodic delta snapshots. (gardener/etcd-backup-restore#84, @swapnilgm)AllowReauth
flag for swift authentication call to true
. (gardener/etcd-backup-restore#80, @georgekuruvillak)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.16.0
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.16.0
delta-snapshot-memory-limit
to restrict memory consumption due to periodic delta snapshots. (gardener/etcd-backup-restore#84, @swapnilgm)AllowReauth
flag for swift authentication call to true
. (gardener/etcd-backup-restore#80, @georgekuruvillak)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.15.2
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.15.2
0.21.0
to 0.20.0
. (5424ccf6787e518c4defb0a3034177adaf4568cf)gardener-apiserver: eu.gcr.io/gardener-project/gardener/apiserver:0.15.1
gardener-controller-manager: eu.gcr.io/gardener-project/gardener/controller-manager:0.15.1