[dashboard]

Action Required

[OPERATOR] This dashboard version requires terminal-controller-manager v0.12.0 or higher, in case the terminal feature is enabled (#792, @petersutter)
[OPERATOR] In case the terminal feature is configured you have to adapt your configuration as it changed incompatible (#739, @petersutter)
- terminal.containerImage in values.yaml needs to be moved to terminal.container.image
- terminal.containerImageOperator in values.yaml needs to be moved to terminal.containerOperator.image

[USER] An error page is shown in case of not found errors (#744, @holgerkoser)
[USER] Terminal Shortcuts: This is a new feature to launch preconfigured terminals for frequently used views. As experimental feature you can also add your own (project specific) terminal shortcuts, if enabled by the admin. See #739 for an example of how to create a project specific terminal shortcut. (#739, @petersutter)

[USER] Fixed: Workers can not be modified via the Dashboard UI if unused zone configurations exist for a cluster (#806, @grolu)
[USER] On the terminal settings dialog you can now choose Auto select node to let the kube-scheduler decide on which node the terminal pod should be scheduled (#795, @petersutter)
[USER] The default load balancer class for new shoot is selected correctly (#787, @holgerkoser)
[USER] Dashboard shows the name of the conflicting service account if you try to add an already existing service account to a project (#783, @holgerkoser)
[OPERATOR] If gardener's APIServerSNI feature gate was enabled by the gardener administrators, it was not possible to reach the kube-apiserver within the terminal pod when running a cluster terminal on the seed (operators only). This is now fixed by using the local endpoint of the kube-apiserver (kube-apiserver / kubernetes.default) instead of the public endpoint. (#792, @petersutter)