[gardener/gardener-extension-registry-cache]

⚠️ Breaking Changes

[USER] The registry.extensions.gardener.cloud/v1alpha2 API version is removed. Use registry.extensions.gardener.cloud/v1alpha3 instead. by @ialidzhikov [#165]
[OPERATOR] The registry.extensions.gardener.cloud/v1alpha2 API version is removed. Before upgrading to this version, make sure that there are no usages of the registry.extensions.gardener.cloud/v1alpha2 API version in the landscape. by @ialidzhikov [#165]

[USER] The registry cache StatefulSets for registries with upstream host with more than 43 chars will be recreated. Only the StatefulSet will be recreated, the underlying PVC remains the same. by @dimitar-kostadinov [#186]

[OPERATOR] This extension is now using the new way of providing monitoring configuration (ref GEP-19) in case a shoot cluster's Prometheus has been migrated to management via prometheus-operator. by @ialidzhikov [#187]
[OPERATOR] The upstream fields in the registry-mirror and registry-cache APIs now support optional port (e.g. example.io:5000). by @dimitar-kostadinov [#183]
[OPERATOR] A new optional remoteURL field in the registry-cache API allows specifying the URL of the upstream registry (e.g. http://example.io:5000). by @dimitar-kostadinov [#183]
[OPERATOR] The registry-cache extension does now support the Deploying Gardener Locally and Enabling Provider-Extensions local setup. by @dimitar-kostadinov [#193]

gardener-extension-registry-cache-admission: europe-docker.pkg.dev/gardener-project/releases/gardener/extensions/registry-cache-admission:v0.9.0
gardener-extension-registry-cache: europe-docker.pkg.dev/gardener-project/releases/gardener/extensions/registry-cache:v0.9.0