[github.com/gardener/dashboard:1.83.0]
⚠️ Breaking Changes
-
[OPERATOR]The backend now requires anwebsocketAllowedOriginsconfiguration to protect the Socket.IO server from cross-site requests -
[USER]Simplified DNS Credential Handling:- DNS credentials no longer require a
SecretBindingorCredentialsBindingto work with the Gardener Dashboard. The Dashboard now relies on a new label,dashboard.gardener.cloud/dnsProviderType: <provider-type>, to identify the DNS provider type. AllSecretresources containing this label will appear as DNS credentials in the Dashboard. - For backward compatibility,
Secretspreviously created through the Dashboard — which have the labelprovider.shoot.gardener.cloud/<provider-type>set by Gardener — will continue to be recognized as DNS credentials. This label now serves as a fallback for existing DNSSecrets. - For new DNS credentials, only a
Secretresource is created (no additionalCredentialsBindingresource). You may safely clean up any existingCredentialsBindingorSecretBindingresources related to DNS credentials, as they are no longer required. by @grolu [#2632]
- DNS credentials no longer require a
-
[DEVELOPER]The dashboard configuration now requires awebsocketAllowedOriginssetting. Without it, the dashboard will not start. See the local development setup documentation for more details. by @grolu [#2588]
✨ New Features
[OPERATOR]Improved Custom Asset Handling[USER]Add providerTemplate for stackit clusters by @nschad [#2686]
Container (OCI) Images
- gardener-dashboard:
europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.83.0