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

1.73.1

[gardener/dashboard]

🐛 Bug Fixes

• [USER] Enhanced volume management for OpenStack workers
  In the last dashboard release, we inadvertently introduced an issue that caused the loss of custom volume sizes for OpenStack workers when they were updated via the dashboard. This release brings a fix to this bug, ensuring that your custom volume configurations are retained post-update.
  Additionally, we've improved the storage size configuration interface. Now, it's easier to distinguish between default and custom volumes. by @grolu [#1722]

Docker Images

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

1.73.0

[gardener/dashboard]

✨ New Features

• [USER] You can now force delete clusters via the dashboard if they are stuck in deletion by @grolu [#1665]
• [USER] Improved cluster messages:
  • Show icons always next to title on cluster details page
  • Fixed overall severity sometimes not correct by @grolu [#1665]
• [USER] Users with the Project viewer role are now able to to download the gardenlogin kubeconfig by fetching the cluster CA via ConfigMap. This feature is anticipated to be supported with Gardener v1.89 and requires gardenlogin v0.5 or higher. by @petersutter [#1708]
• [OPERATOR] Add support for IronCore as infrastructure provider by @afritzler [#1700]

🐛 Bug Fixes

• [USER] Fixed invalid default minimum volume size limits for clusters without a limit defined in the cloud profile. Also improved handling for machine types without storage or volume defined in the cloud profile by @grolu [#1701]
• [USER] Terminal: fixed an issue where the loading spinner would not disappear, even though the terminal pod is running and the terminal connection shows as connected by @petersutter [#1702]
• [USER] Fixed an issue that caused dark theme color to be applied to some alert messages by @grolu [#1665]
• [USER] Action dialogs fixes:
  • We've addressed an issue where tooltips were missing for some disabled cluster action buttons. Users will now see helpful tooltips providing more context on why these actions are currently unavailable
  • Fixed issues with line breaks in the tooltips for certain buttons, ensuring that the tooltip text is now displayed correctly and is easier to read
  • Resolved problems related to the display of precondition constraint failure messages during maintenance operations
  • Fixed an issue where some action buttons were visible to users who did not have permission to perform those actions. This update ensures that the interface correctly reflects available actions based on user rights by @grolu [#1697]

Docker Images

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

1.72.0

[gardener/dashboard]

⚠️ Breaking Changes

• [USER] Removed support for deprecated annotations. These annotations have been deprecated long time ago:
  • garden.sapcloud.io/createdBy. If you still have a cluster using this annotation, you can migrate it manually to dashboard.gardener.cloud/created-by if you need to
  • shoot.garden.sapcloud.io/ignore: If you still have a cluster using this annotation, you can migrate it manually to shoot.gardener.cloud/ignore if you need to by @grolu [#1669]

✨ New Features

• [USER] Streamlined Kubernetes cluster upgrades for enhanced user experience. We've removed non-eligible versions from the upgrade selection, replacing them with a hint to indicate the existence of more versions. Additionally, only supported versions are now highlighted on the version chip. To aid in version management, chips for deprecated versions will now display in a warning color, alerting users to the need for an upgrade by @grolu [#1683]
• [USER] Hidden GitHub comments will no longer be displayed on the Cluster Details page. by @holgerkoser [#1675]
• [USER] Added support to request a time-limited kubeconfig on the cluster details page. The lifetime can be configured on the settings page. This feature is disabled by default and can be enabled by the gardener dashboard operator. by @grolu [#1666]
• [OPERATOR] The feature to request a time-limited kubeconfig is disabled by default. You can enabled it via .Values.global.dashboard.frontendConfig.shootAdminKubeconfig.enabled. The maximum expiration seconds can be controlled via .Values.global.dashboard.frontendConfig.shootAdminKubeconfig.maxExpirationSeconds. by @grolu [#1666]

🐛 Bug Fixes

• [USER] The broken link to the permission configuration documentation for Azure secrets was fixed. by @MrBatschner [#1667]
• [USER] Fixed an issue on the member management page. Update members and service account dialog did not render correctly because of an issue with the input validation by @grolu [#1686]
• [USER] Project list: fixed issue where the second entry is highlighted on key-down in some cases by @petersutter [#1687]
• [USER] Fixed email check for account names: Non email user accounts are no longer converted to a mailto link by @grolu [#1669]
• [USER] Resolved an issue from Dashboard version 1.70 that prevented the display of descriptions in the 'Update Cluster Version' dropdown selection by @grolu [#1672]
• [USER] Improved Navigation in project list filter: Disabled spell check to enhance arrow key navigation reliability. This update addresses an issue where spell check functionality occasionally interfered with keyboard navigation by @grolu [#1696]
• [USER] Resolved a styling issue that affected the hover functionality in the Safari browser by @grolu [#1696]

🏃 Others

• [USER] Introduced tonal variations to our chips and alert designs, previously defined with outline styles by @grolu [#1681]

📖 Documentation

• [USER] Enhanced the Connect Kubectl documentation by @petersutter [#1679]
• [DEVELOPER] Updated the Project Operations kubeconfig documentation by @n-boshnakov [#1673]

Docker Images

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

1.71.1

[gardener/dashboard]

🐛 Bug Fixes

• [USER] Fixed an issue where the error message _all is not a function was displayed on the ALL PROJECTS page. by @holgerkoser [#1663]

Docker Images

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

1.71.0

[gardener/dashboard]

⚠️ Breaking Changes

• [OPERATOR] Change OCI Image Registry from GCR (eu.gcr.io/gardener-project) to Artifact-Registry (europe-docker.pkg.dev/gardener-project/releases) by @ccwienk [#1645]

✨ New Features

• [USER] Enhanced Client-Side Validation:
  Previously, if there was a validation error, the submit buttons on Dialogs and the Create Cluster page would be greyed out. Now, these buttons remain active even if there is a validation error.
  Clicking on the submit button in the presence of a validation error will not execute the submit logic. Instead, it will trigger the validation process to ensure that all validation error messages are clearly visible at the respective input fields.
  In addition, we've made it easier to view all error messages. They are now collected and displayed in an alert, similar to how server-side error messages are shown. This enhancement ensures that users are fully aware of any errors that prevent to proceed with the action. by @grolu [#1633]
• [USER] An improvement in performance and memory usage on the shoot list has been achieved when a large number of clusters are present. In the past, under heavy load, there were repeated instances where the dashboard became unresponsive due to very high memory consumption. This has been achieved by implementing the following two changes:
  • Throttling of shoot events in the frontend.
    Now, only the uid of the modified object is sent to the client, coupled with periodic synchronization of associated shoots.
  • Removal of the key property in the g-shoot-list-row component
  • Improved performance of sorting and filtering implementation
  • Faster response times for list shoot request (experimental: must be enabled by an operator)
  • Reduced network traffic for invisible browser tabs by @holgerkoser [#1637]
• [OPERATOR] Added a configuration parameter Values.global.dashboard.maxRequestBodySize that specifies the maximum size of the request body. It's value defaults to 100kb. by @holgerkoser [#1656]
• [OPERATOR] Experimental Features:
  • Enhanced Watch Cache Control for List Shoots Requests.
    We've introduced a new feature to fine-tune caching behavior for list shoots requests. A new configuration option, Values.global.dashboard.experimentalUseWatchCacheForListShoots, has been added to the gardener-dashboard Helm chart. This allows for more precise control over caching with four settings: never, no, yes, and always. By default, this is set to never. As an experimental feature, we welcome feedback and suggest caution in production environments.
  • Fine-tune the throttle delay per cluster.
    This option, found under Values.global.dashboard.frontendConfig.experimental.throttleDelayPerCluster, allows administrators to set the base number of milliseconds delay per cluster. This delay dynamically adjusts the synchronization throttle based on the number of active clusters, optimizing performance and resource utilization in environments with a varying number of clusters. by @holgerkoser [#1637]

🐛 Bug Fixes

• [OPERATOR] Fixed garden cluster terminals when the host cluster is a managed Seed by @petersutter [#1657]
• [OPERATOR] Dashboard pods were not recreated after assets have been changed by @petersutter [#1627]
• [USER] Fixed issues with the machine image input field:
  • image description was not shown
  • certain mache image hints were not shown when editing the worker for an existing shoot by @petersutter [#1635]
• [USER] Fxed issue where the kubernetes dashboard was not shown on cluster details page in case the addon was enabled. The issue occurs when static token kubeconfig is disabled. by @petersutter [#1658]
• [USER] Fixed the owner selection via mouse click on the project administration page. by @holgerkoser [#1632]
• [USER] Fixed issue on create cluster page: On error, alert should scroll into view by @petersutter [#1629]
• [USER] Users will now be redirected back to the last visited URL after automatic logout due to session timeout or authentication errors. by @holgerkoser [#1624]
• [USER] Fixed several bugs on the project filter menu. More details in this PR by @petersutter [#1623]
• [USER] Fixed vSphere Load Balancer Class selection by @grolu [#1625]

Docker Images

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