[dashboard]

⚠️ Breaking Changes

[OPERATOR] The gardenctl-v2 commands that can be copied from the cluster details page to target the "Cluster" or the "Control Plane" will not include the command to set the KUBECONFIG environment variable anymore (e.g. eval $(gardenctl kubectl-env bash) in case of bash) (gardener/dashboard#1158, @petersutter)
- A warning message is displayed when running the target command in case the KUBECONFIG environment variable does not point to the current target
- The rc command startup script sets the KUBECONFIG variable when evaluating the command output, usually as part of the shell profile, e.g. source <(gardenctl rc bash) in case of bash. Requires gardenctl v2.1.0
- If you do not load the gardenctl rc command in your shell profile or do not have the gk or, with bash as an example, eval "$(gardenctl kubectl-env bash)" in your bash profile, you will have to run it manually in order to have the KUBECONFIG point to the kubeconfig of the current target

[USER] Added a warning to configure workers dialog in case additional zones require additional network configuration (gardener/dashboard#1194, @grolu)
[USER] Added support for Azure Private DNS (gardener/dashboard#1191, @grolu)
[USER] Several improvements for the readiness chips (gardener/dashboard#1190, @grolu)
- Sort readiness chips by name
- Left align readiness tags, this improves overview if additional chips are present for only some of the clusters
- Fill chips that have an error state (to make them more prominent)
- Added icons for readiness chips that have a state other than success
[USER] Improved worker CIDR generation for new clusters when using non default node networks (gardener/dashboard#1182, @grolu)
[OPERATOR] Improved visibility of user errors (gardener/dashboard#1193, @grolu)
[OPERATOR] Default node CIDR can be overwritten by setting the new frontend.defaultNodesCIDR value in the Dashboard configuration (gardener/dashboard#1182, @grolu)

[USER] When selecting a machine image that does not support the currently selected container runtime, the Dashboard does no longer implicitly set the container runtime to something else (gardener/dashboard#1199, @grolu)
[USER] Fixed an issue caused by wildcard Floating IP names not mapped correctly, therefore available load balancer classes were not shown on shoot details page. Also the UI did not flag the default load balancer class (gardener/dashboard#1198, @grolu)
[USER] Service Accounts with more than one secret are now handled correctly (gardener/dashboard#1195, @grolu)

[DEPENDENCY] Updated docforge version and simplified path transformations in docforge manifest (gardener/dashboard#1169, @Kostov6)