v0.10.0

[gardener/gardener-extension-registry-cache]

⚠️ Breaking Changes

• [OPERATOR] The legacy method of providing monitoring configuration via ConfigMaps labeled with extensions.gardener.cloud/configuration=monitoring has been removed. The extension does now only uses the new contract for providing monitoring configuration. Before upgrading to this version of the extension, make sure that the deployed Gardener version supports the new monitoring contract. by @dimitar-kostadinov [#237]

📰 Noteworthy

• [DEVELOPER] The containerd registry configuration hosts.toml files are now created using the OpetingSystemConfig CRI API. by @dimitar-kostadinov [#227]

🏃 Others

• [OPERATOR] A priorityClassName can now be set for the admission deployment via the admission Helm chart. by @timuthy [#222]
• [OPERATOR] The registry-cache admission validation is skipped when no semantic change in providerConfig is detected. by @dimitar-kostadinov [#210]
• [OPERATOR] The following image is updated:
  • europe-docker.pkg.dev/gardener-project/releases/3rd/registry: 3.0.0-alpha.1 -> 3.0.0-beta.1 by @ialidzhikov [#224]

Docker Images

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