[ci:component:github.com/gardener/dashboard:1.68.2->1.70.1]

[gardener-robot-ci-2]

Release Notes:

`spec.ingressClassName` is now set to `nginx` for the dashboard `Ingress`. You can change the default in the `values.yaml` file by adjusting the property `global.dashboard.ingress.ingressClassName`.

Allow customization of dashboard branding like product logo, name, title, slogan and custom html templates for teaser and footer. The documentation and a detailed example can be found in the dashboard operation guidelines https://github.com/gardener/dashboard/blob/master/docs/operations/customization.md

Enhanced the `gardener-dashboard` helm chart with additional configuration options:
* Browser window title is now customizable via `Values.global.dashboard.frontendConfig.branding.documentTitle`
* Manual configuration of OIDC redirect URLs is supported through `Values.global.dashboard.oidc.redirectUris`. This is particularly useful for local development setups

Terminals: As gardener took over the responsibility of providing kube-apiserver endpoints with trusted certificates the `terminal-bootstrap` component was dropped. Make sure to clean up the created resources of the terminal bootstrapper. See PR description for more details.

If the login session in the dasboard expires the user no longer gets an error message `JWT expired`. In case of autoLogin is enabled the user is redirected back to the last visited page

The terms `Grafana` and `Loki` are replaced with `Plutono` and `Vali` to reflect the change in `gardener/gardener@v1.71.0`.

Fixed hibernation schedule time input for Safari browser

Github app authentication is now supported (in addition to token authentication) for the ticket feature

Fixed duplicative tooltip on issue since value

Fixed a typo in shoot credentials rotation

Implementation of lazy loading for copy to clipboard functionality

The `gardener-dashboard` `Deployment` now runs with high availability config (with label `high-availability-config.resources.gardener.cloud/type=server`). For more information about the HA config see [resource-manager.md#high-availability-config](https://github.com/gardener/gardener/blob/master/docs/concepts/resource-manager.md#high-availability-config)

Enable focus mode for regular project lists. This feature used to be exclusive for operators. It can now be used by regular users on all cluster lists. This feature enables users to get a static overview of clusters with issues. In order to use this feature, you need to enable it on the `Settings` page.

Fixed an issue where the filter on the `Secrets`, `Members` and `Clusters` page was not reset when switching the Project

Added functionality to create, view and manage workerless clusters

Terminal: By default, the access service account within the garden terminal pod is bound to `gardener.cloud:system:administrators`, not `cluster-admin` anymore.

Fixed code completion and tooltips in cluster editor: Recent Gardener releases dropped support for OpenAPI v2. Dashboard now uses OpenAPI v3 to fetch shoot resource information

You can now set annotations and labels for the dashboard deployment, allowing you to set e.g. the `high-availability-config.resources.gardener.cloud/type=server` label

Terminals: The `connectSrc` directive of the Content Security Policy no longer permits the use of `wss:` by default. You need to set up the allowed hosts that the browser can connect to for the web terminal feature. This can be done using `Values.global.terminal.allowedHostSourceList`. For more details see [webterminals.md#allowlist-for-hosts](https://github.com/gardener/dashboard/blob/master/docs/operations/webterminals.md#allowlist-for-hosts)

In addition to the `defaultNodesCIDR` config (`Values.global.dashboard.frontendConfig.defaultNodesCIDR`) of the `gardener-dashboard` which applies for all new Shoots, you can now have a configuration per cloud profile, by setting `.spec.providerConfig.defaultNodesCIDR` on the respective `CloudProfile`

Fixed two memory leaks in `GTimeString` and `localStorage` store. This issue was causing an unnecessary allocation of memory, which, over time, led to degraded UI performance and eventually leading to Out of Memory crashes.

The `dashboard` chart allows to optionally configure a projected volume based kubeconfig

An error will now be logged in case the OIDC issuer discovery fails

This release includes nodejs `v20.8.1`

Migrated frontend code to Vue 3 and Vuetify 3 UI components. Vue 2 will reach [End of Life](/https://v2.vuejs.org/lts/) (EOL) on December 31st, 2023

Added an input field to configure the maintenance time window duration. The textfield hints now show the UTC begin and end time

The default grant types for the garden cluster OIDC kubeconfig have changed to `auto`, `authcode` and `device-code`. `authcode-keyboard` was removed and `device-code` grant type was added. The default grant types can be overridden by setting `Values.global.dashboard.frontendConfig.grantTypes` in the `gardener-dashboard` helm chart

Tickets are no longer automatically closed by the dashboard when a shoot is deleted. This should be handled by a different component instead, like a robot.

The Helm chart are now adapted such that they work well in garden cluster with enabled `NetworkPolicy` protection (default since `gardener/gardener@v1.71` when garden cluster is managed by `gardener-operator`).

Users with permission to `list` all `projects` can see them now in the dashboard. Previously the permission to `get` `secrets` across all namespaces was required.

Terminal: You can now configure the role bindings to which the access service account within the `garden` terminal pod is bound (`Values.global.terminal.garden.roleBindings`).

[gardener-robot]

@gardener-robot-ci-2 Thank you for your contribution.