1.78.0

[gardener/dashboard]

⚠️ Breaking Changes

• [OPERATOR] Cost Object: You must migrate existing configurations to the new format. Previously, the configuration used Values.global.dashboard.frontendConfig.costObject. It should now be updated to Values.global.dashboard.frontendConfig.costObjects, which is a list of objects. Each object in this list must include a type property, alongside existing properties such as title, description, and regex. by @petersutter [#2102]
• [USER] Removed the ability for users to retrieve their token from the My Account page. by @petersutter [#2131]

✨ New Features

• [USER] Header warnings returned by the Kubernetes API server are now displayed as notifications in the Gardener dashboard. This includes important messages like deprecation warnings. Additionally, admission webhooks may provide custom warnings in the headers by @grolu [#2033]
• [USER] Upgraded the code editor from CodeMirror 5 to CodeMirror 6 to enhance performance, modernize the interface, and improve extensibility by @grolu [#2058]
• [USER] Support Azure Cloud Configuration for DNS Secrets by @grolu [#2034]
• [OPERATOR] Enhanced cost object configuration to support multiple cost object types. The selected type is now stored under Project.annotations["billing.gardener.cloud/costObjectType"]. by @petersutter [#2102]

🐛 Bug Fixes

• [USER] Fixed issues with hibernation schedule dialog: reset button and time saving by @petersutter [#2076]
• [USER] Consider all seeds for Shoot migration and add warning for provider mismatch by @petersutter [#2079]
• [USER] To enhance the overview and readability of the cluster list, particularly in environments constrained by space or containing an abundance of information, we have introduced a feature that allows items to be collapsed when they are displayed in the cluster list. by @grolu [#1991]
• [USER] Fixed display issues with minimum volume size by @grolu [#2030]

🏃 Others

• [USER] The option to rotate the SSH keypair is hidden when SSH access is disabled. by @petersutter [#2077]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.78.0

1.77.0

[gardener/dashboard]

✨ New Features

• [USER] Adds line selection highlighting in the Shoot YAML editor when selecting the line numbers. The line selection is reflected in the URL. by @petersutter [#1982]
• [USER] Available purposes now depend on enabled add-ons, which can only be activated if the purpose is set to evaluation. Hints have been added to explain potential limitations in purpose selection by @grolu [#2031]

🐛 Bug Fixes

• [USER] Resolved an issue where updates to existing worker groups would fail if an unused zone network configuration was present by @grolu [#2048]
• [USER] chart: An issue causing the controlledValues: RequestsOnly field not to be set for the gardener-dashboard-vpa VPA is now fixed. by @ialidzhikov [#2017]
• [OPERATOR] Upgraded the gardener dashboard to use Node.js version v22.7 which resolves CVE-2024-24806 by @holgerkoser [#2063]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.77.0

1.76.2

[gardener/dashboard]

🐛 Bug Fixes

• [USER] We have addressed an issue affecting the worker group zone configuration for existing Azure clusters by @grolu [#2003]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.76.2

1.76.1

[gardener/dashboard]

🐛 Bug Fixes

• [USER] Fixed a bug where navigating between cluster details pages caused new ticket titles to inherit the title from the previously viewed cluster by @petersutter [#1976]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.76.1

1.76.0

[gardener/dashboard]

⚠️ Breaking Changes

• [USER] DNS configuration is now maintained under spec.extensions. When modifying the DNS configuration of an existing shoot, the settings will be migrated to this new location, and the syncProvidersFromShootSpecDNS flag will be set to false by @grolu [#1888]
• [USER] The basic auth observability URLs and credentials are hidden if the OIDC observability URLs are displayed. Instead, fetch the credentials from the <shootname>.monitoring Secret. See also gardener/gardener#9867 by @petersutter [#1899]
• [DEVELOPER] The local Vite dev server now starts on HTTPS at https://localhost:8443 instead of http://localhost:8080. Run yarn setup to generate a server certificate and add the CA to the macOS keychain. by @holgerkoser [#1894]

✨ New Features

• [USER] Added support for DDNS / RFC2136 DNS provider by @grolu [#1889]
• [USER] Reflect search query on project clusters page in URL by @petersutter [#1952]
• [USER] The OIDC observability URLs can now be displayed for Shoot clusters, if enabled by the administrator by @petersutter [#1899]
• [USER] You can now configure custom shoot fields directly from the dashboard using the new editor, eliminating the need to use kubectl. by @petersutter [#1926]
• [USER] Enhanced DNS configuration logic to configure extension DNS settings in the spec.extensions section by @grolu [#1888]
• [OPERATOR] In order to mitigate Cross-Site Request Forgery (CSRF) attacks a random value is now part of the state parameter during the OIDC authorization code flow. by @holgerkoser [#1894]
• [OPERATOR] Added host-prefix to all cookie names. by @holgerkoser [#1894]

🐛 Bug Fixes

• [DEVELOPER] Fixed debugging issues by updating vscode-jest-runner config and scripts. by @holgerkoser [#1923]

🏃 Others

• [USER] Readiness Chips improvement: All Shoot constraints that are not in the condition status != "True" are shown. This includes conditions with statuses "False", "Unknown" and "Progressing". Previously, only constraints with an error code were displayed. by @petersutter [#1887]
• [DEVELOPER] Refactored store to use context and getters, and improved frontend components by eliminating fuzzy interfaces and direct store data mapping for better maintainability and quality. by @holgerkoser [#1838]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.76.0

1.74.2

[gardener/dashboard]

🐛 Bug Fixes

• [USER] Fixed an issue where the shoot details page could not be loaded when GitHub comments could not be fetched by @petersutter [#1905]

Docker Images

• dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.74.2

1.75.1

[gardener/dashboard]

🐛 Bug Fixes

• [USER] Fixed an issue where the shoot details page could not be loaded when GitHub comments could not be fetched by @petersutter [#1898]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.75.1

1.75.0

[gardener/dashboard]

✨ New Features

• [USER] The Dashboard now recognizes and displays automatic update notifications according to the configured update strategy for machine image vendors by @grolu [#1807]
• [OPERATOR] Promoting experimentalUseWatchCacheForListShoots to Stable
  • The experimentalUseWatchCacheForListShoots feature flag in the gardener-dashboard Helm chart, which was introduced with #1637, has now been promoted to stable and removed. Previously, this feature was gated behind the Values.global.dashboard.experimentalUseWatchCacheForListShoots Helm chart value. With this release, the feature is now enabled by default, which is equivalent to setting Values.global.dashboard.experimentalUseWatchCacheForListShoots: always by @petersutter [#1822]
• [OPERATOR] The dashboard supports a previous session secret. It allows for a seamless rotation of the session secret by supporting both the current and previous secrets. When installed using the helm chart, provide Values.global.dashboard.sessionSecretPrevious. Set this value to the previous sessionSecret during secret rotation, and leave it empty otherwise. by @petersutter [#1856]

🐛 Bug Fixes

• [USER] Fixed: Addressed an issue where the Dashboard incorrectly reported no available update paths to a Kubernetes version when no immediate supported minor version updates were available by @grolu [#1848]
• [USER] During session secret rotation, an unexpected error with code 500 could occur, requiring manual deletion of session cookies to resolve. This situation is now properly handled, and the user will be redirected to the login page accordingly. by @holgerkoser [#1869]

🏃 Others

• [USER] The last error description of the Terminal resource is shown on timeout. by @petersutter [#1810]
• [OPERATOR] Terminal: terminal-controller-manager v0.32.0 required in order to display the last error description of the Terminal resource. by @petersutter [#1810]
• [OPERATOR] The component name is changed from dashboard to gardener-dashboard. by @ialidzhikov [#1857]
• [OPERATOR] The Helm chart was adapted to mount Kubernetes secrets as read-only files instead of storing them as environment variables, in order to comply with DISA STIG V-242415. by @petersutter [#1842]
• [OPERATOR] Values.global.dashboard.oidc.clientSecret is now optional. The dashboard can now also use a public OIDC client. by @petersutter [#1835]
• [DEVELOPER] The Lease object is no longer included in the Helm chart. Instead, it is now created dynamically during runtime if it does not already exist by @petersutter [#1823]

Docker Images

• gardener-dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.75.0

1.74.1

[gardener/dashboard]

🐛 Bug Fixes

• [USER] Ticket titles start with [<projectName>/<shootName>], unless overridden by a Gardener administrator's configuration. by @petersutter [#1830]

Docker Images

• dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.74.1

1.74.0

[gardener/dashboard]

⚠️ Breaking Changes

• [OPERATOR] Changes have been made to two gardener-dashboard Helm chart values related to the ticket feature:
  • The value previously at Values.global.dashboard.frontendConfig.ticket.newTicketLabels has been moved to Values.global.dashboard.frontendConfig.ticket.newIssue.labels.
  • The value previously at Values.global.dashboard.frontendConfig.ticket.issueDescriptionTemplate has been moved to Values.global.dashboard.frontendConfig.ticket.newIssue.body. by @petersutter [#1775]

✨ New Features

• [USER] To enhance user experience and minimize premature notifications, we've implemented a new feature in the update notification system. Now, an update alert for Kubernetes and machine image versions will only be displayed if the current version is set to expire within the next 30 days. This adjustment ensures that users receive timely reminders without unnecessary warnings for versions expiring in the more distant future by @grolu [#1746]
• [USER] Route information is now included in the browser window title by @grolu [#1752]
• [USER] Added Fallback Solution for Non-SemVer Compatible Machine Image Versions: In previous versions, machine images from some vendors that did not adhere to Semantic Versioning (SemVer) standards were omitted from the user view in the dashboard. This was due to the Dashboard's strict adherence to SemVer for sorting and presenting image versions, resulting in non-compliant versions being filtered out. To address this, we now try to normalize those versions to make them SemVer compliant. If this is not possible, affected versions will still be filtered out. by @grolu [#1734]
• [USER] Several improvements to version and worker chips:
  • Version & Worker Group Chips: Now, both show in a warning color if deprecated, offering a clear visual cue for items needing updates. The version chip also reveals detailed info, including classification and expiration, with a click.
  • Cluster Management: Updating clusters is now streamlined under the actions menu on the cluster list page for easier access.
  • Consistent UI: Version information now appears as a chip on cluster details, aligning with the display of worker chips for a unified look. by @grolu [#1758]
• [OPERATOR] GitHub issue forms are now supported when creating new tickets (GitHub issues) from the dashboard.
  • Set Values.global.dashboard.frontendConfig.ticket.newIssue.template to specify the filename of the issue form template. For more information, refer to the GitHub documentation
  • To pre-fill template form elements, specify the id of the form element under Values.global.dashboard.frontendConfig.ticket.newIssue. For instance, if you have a form element with id affectedCluster, you can pre-fill it like this: Values.global.dashboard.frontendConfig.ticket.newIssue.affectedCluster="${shootUrl}". The template variable shootUrl will be replaced during runtime with the actual dashboard link of the shoot cluster. by @petersutter [#1775]

🐛 Bug Fixes

• [USER] Fixed a bug that allowed to bypass the GDialog confirmation using by @grolu [#1751]
• [USER] Resolved Chrome Warnings and Enhanced Performance by Streamlining Font Formats for Material Design Icons: In our latest update, we've optimized the @font-face definition for Material Design Icons by removing the OpenType (.eot) and TrueType (.ttf) font formats. This adjustment significantly enhances the performance and reduces the bandwidth usage of our dashboard web application, ensuring a smoother and more efficient user experience. by @holgerkoser [#1731]
• [USER] Fixed an issue that caused quotas using numerical abbreviations (e.g., '1k') to not be displayed correctly in the Gardener Dashboard by @grolu [#1719]

🏃 Others

• [USER] The gardenlogin kubeconfig now only includes kube-apiserver addresses from Shoot.status.advertisedAddresses. This ensures compatibility with gardener/gardener version v1.91.0 and later. by @petersutter [#1750]

Docker Images

• dashboard: europe-docker.pkg.dev/gardener-project/releases/gardener/dashboard:1.74.0