1.55.0

[dashboard]

⚠️ Breaking Changes

• [OPERATOR] For the terminal bootstrapping ingress resources are now created using the [networking.k8s.io/v1](http://networking.k8s.io/v1) API group. This requires seeds to run kubernetes v1.19 or higher (gardener/dashboard#1185, @grolu)
• [OPERATOR] Make sure that the k8s cluster on which the dashboard will be deployed is on version v1.19.0 or higher. Older versions are not supported anymore (gardener/dashboard#1173, @Wieneo)
• [OPERATOR] The creation of infrastructure secret functionality now requires gardener-apiserver version >= v1.38.0. (gardener/dashboard#1154, @ialidzhikov)

✨ New Features

• [OPERATOR] Use configured apiServerCaData value for generated service account kubeconfigs (gardener/dashboard#1181, @grolu)
• [OPERATOR] Add support for new monitoring secrets gardener/gardener#5608 (gardener/dashboard#1178, @grolu)

🐛 Bug Fixes

• [USER] Fixed a bug that caused the maintenance constraint message not showing the actual cause (gardener/dashboard#1165, @grolu)
• [OPERATOR] Allow configuration of the node CLI options in order to optimize garbage collector. (gardener/dashboard#1179, @holgerkoser)
• [OPERATOR] Fixed an issue preventing HELM from creating the necessary ingress resources on K8s >=v1.22.0 (gardener/dashboard#1173, @Wieneo)

🏃 Others

• [OPERATOR] The Gardener dashboard now specifies the SecretBinding provider.type field when creating SecretBindings (gardener/dashboard#1154, @ialidzhikov)

1.54.0

[dashboard]

✨ New Features

• [USER] You can now switch between legacy gardenctl and gardenctl-v2 commands on the My Account page. You can also choose your preferred shell for which the commands on the cluster details page will be adapted. (gardener/dashboard#1148, @petersutter)

🐛 Bug Fixes

• [USER] There may be situations in which cookies are deleted or lost in the browser. In this case the shoot cluster list was always empty until the user logged in again. Now in this case a logout is forced and the user is redirected to the login screen. (gardener/dashboard#1145, @holgerkoser)
• [OPERATOR] Up to now, connection errors were always output twice and again and again in the log. Now an error appears only once in the log, because the clients log out automatically in case of connection problems and we changed from several socket.io namespaces to only one (default) namespace. (gardener/dashboard#1145, @holgerkoser)

1.52.3

[dashboard]

🐛 Bug Fixes

• [USER] Fixed missing ControlPlaneConfig zone value for hcloud (gardener/dashboard#1135, @NotTheEvilOne)
• [OPERATOR] Support gardener error codes in the cluster search field (gardener/dashboard#1137, @holgerkoser)
• [DEVELOPER] Fixed a bug so that the server runs on macOS Monterey (gardener/dashboard#1130, @holgerkoser)

🏃 Others

• [USER] Added an additional warning message when changing cloud provider secrets to clarify when the change will become active for Shoot owners (gardener/dashboard#1134, @BeckerMax)

1.52.2

[dashboard]

🐛 Bug Fixes

• [USER] Fixed an issue that caused Configure Workers dialog to break if a cluster has an outdated worker image configured that is no longer in the list of supported images (removed from cloud profile) (gardener/dashboard#1113, @grolu)
• [OPERATOR] Fixed the terminal pod for the garden cluster in case the hosting cluster (seed) for the garden web-terminal pods is different than the cluster that hosts the gardener apiserver (gardener/dashboard#1118, @petersutter)
• [OPERATOR] Dex is upgraded to v2.30.0 fixing SM2 Decryption Buffer Overflow (CVE-2021-3711) (gardener/dashboard#1112, @grolu)

1.52.1

[dashboard]

🐛 Bug Fixes

• [USER] Shoot status: Fixed error handling for unknown error codes (#1109, @grolu)
• [USER] Fixed shoot control plane migration detection (progress indicator) (#1109, @grolu)
• [USER] Fixed: Popovers cannot be closed with the close button (#1106, @grolu)
• [USER] Fixed a problem on the cluster details page where a 410 error message is displayed even though the cluster exists and is available (#1105, @holgerkoser)

1.52.0

[dashboard]

🐛 Bug Fixes

• [USER] Solves a problem when a user has rotated a service account secret. In the frontend an error message was erroneously displayed, which is fixed now. (#1095, @holgerkoser)
• [USER] Fix HCloud Secret Dialog (#1094, @gesslein)
• [USER] Fixes the problem that scroll bars are displayed in the UI even if there is enough space available. (#1087, @holgerkoser)

1.51.3

[dashboard]

🐛 Bug Fixes

• [USER] Fixed a memory leak in the cluster list. The memory consumption of the browser increased over time until finally the corresponding process crashed. (#1092, @holgerkoser)

1.51.2

[dashboard]

🐛 Bug Fixes

• [USER] Fixed a problem in the DNS provider configuration that caused a newly added DNS provider to always be disabled on an existing cluster (#1086, @holgerkoser)
• [USER] Fixed some issues regarding creating and editing worker groups (#1084, @grolu)
  • Existing worker groups may keep cri.name empty without failing validation
  • Additional container runtimes selection did no longer show up
  • Machine worker.machine.image included internal properties in create shoot editor
• [USER] Fixed an issue in the TicketComment component causes it not to be rendered anymore (#1080, @holgerkoser)
• [USER] Fixes a bug with the size of dialogs. In some cases the dialogs were too small to display the complete content clearly. The size of all dialogs has been adjusted and unified (#1075, @holgerkoser)

1.51.1

[dashboard]

🐛 Bug Fixes

• [USER] Fixed an issue on the cluster creation page where the networking section was empty because of a permission issue: Users could not read list of networking types and registered dns provider extensions (#1074, @grolu)

1.51.0

[dashboard]

⚠️ Breaking Changes

• [OPERATOR] The Dashboard no longer adds dockerto the list of available CRIs. You need to adapt all CloudProfiles and explicitly add docker to all MachineImageVersions which support it (#1059, @grolu)

✨ New Features

• [USER] Container Runtime is now a required field for cluster workers and defaulted to containerd for cluster kubernetes versions 1.22 and higher. Clusters with older kubernetes versions keep docker as default container runtime. If default runtime is not in the list of supported runtimes of a machine image it defaults to the first one specified in the cloud profile (#1059, @grolu)
• [USER] Added support to authenticate against GKE clusters using google service account key. In this case, the referenced secret needs to have the serviceaccount.json data key in addition to the kubeconfig data key (#1058, @holgerkoser)
• [USER] Container runtimes of existing workers can now be changed (#1044, @grolu)
• [USER] Support for the hetzner cloud extension (hcloud) (#1043, @poelzi)
• [USER] External DNS Provider Support (#1026, @grolu)
  • Add and manage DNS Provider Secrets
  • Configure Shoot DNS Providers
• [USER] Added extended search capabilities to cluster search: (#1021, @grolu)
  • Search params are now ANDed, allowing one to refine the search
  • Use quotes for exact words or phrases
  • Use minus sign to exclude words that you don't want
• [OPERATOR] It is now possible to add configurable hints for machine image vendors (#1066, @grolu)
• [OPERATOR] Added support for ERR_RETRYABLE_INFRA_DEPENDENCIES and ERR_INFRA_REQUEST_THROTTLING error codes (#1040, @grolu)
• [OPERATOR] The option to Hide user issues for operators has been replaced by an option to remove both user issues and temporary issues. This new filter is labelled as Hide no operator action required issues (#1040, @grolu)

🐛 Bug Fixes

• [USER] Preserve the initial URL hostname during the OIDC login process (#1054, @holgerkoser)
• [USER] Fixed an issue where the terminal container was not created with privileged set to true of the containers securityContext when enabling the Privileged flag on the terminal settings UI (#1051, @petersutter)

📖 Documentation

• [OPERATOR] Please note the following changes in the values.yaml file of the gardener-dashboard helm chart: (#1054, @holgerkoser)
  • The configuration property .Values.oidc.redirectUri is no longer used and has been removed. Instead, the list of valid OIDC redirect URIs is determined based on the ingress hosts .Values.ingress.hosts. If tls .Values.ingress.tls is active the redirect URI scheme is assumed to be https for all hosts.