Skip to content

Releases: gardener/dashboard

1.61.3

04 Nov 13:53
Compare
Choose a tag to compare

[dashboard]

πŸ› Bug Fixes

1.61.2

18 Oct 18:26
Compare
Choose a tag to compare

[dashboard]

⚠️ Breaking Changes

πŸ› Bug Fixes

1.61.1

08 Oct 08:26
Compare
Choose a tag to compare

[dashboard]

πŸ› Bug Fixes

1.61.0

07 Sep 07:33
Compare
Choose a tag to compare

[dashboard]

✨ New Features

  • [USER] Static token kubeconfig cluster access can be disabled for new and existing clusters (gardener/dashboard#1249, @grolu)
  • [USER] Projects are now also visible if the phase is not Ready. In this case the project has a warning icon next to the name (gardener/dashboard#1252, @grolu)
  • [USER] Added architecture selection to worker group configuration (gardener/dashboard#1261, @grolu)
  • [OPERATOR] Operators can now trigger control plane migration via a configuration dialog. The configuration button is hidden for regular users, unless they have been granted permission to trigger a control plane migration for their shoots (gardener/dashboard#1262, @grolu)
  • [OPERATOR] Automatically reload referenced data of the dashboards kubeconfig. This is necessary for the Service Account Token Volume Projection feature (gardener/dashboard#1232, @holgerkoser)
  • [OPERATOR] Clusters that have the dashboard.gardener.cloud/ignore-issues annotation are filtered on the All Projects page in case the Hide no operator action required issues filter is checked (gardener/dashboard#1271, @petersutter)

πŸ› Bug Fixes

πŸƒ Others

1.60.0

26 Jul 08:32
Compare
Choose a tag to compare

[dashboard]

πŸ› Bug Fixes

πŸƒ Others

1.59.0

04 Jul 13:05
Compare
Choose a tag to compare

[dashboard]

⚠️ Breaking Changes

  • [USER] The feature to rotate the service account secrets was removed. Instead you now have to delete the service account if you want to invalidate all tokens that were issued for your service account (gardener/dashboard#1234, @petersutter)
  • [USER] Downloaded kubeconfigs for service accounts on the project Members page now have tokens that will expire by default in 90 days, except if the kube-apiserver is configured with a shorter maximum validity duration or the dashboard's default was changed by your landscape administrator (gardener/dashboard#1234, @petersutter)
  • [OPERATOR] This Dashboard version is not compatible with Gardener versions prior v1.48.x (gardener/dashboard#1216, @petersutter)
  • [OPERATOR] Downloaded kubeconfigs for service accounts on the project Members page have tokens that will expire by default in 90 days, except the kube-apiserver is configured with a shorter maximum validity duration (--service-account-max-token-expiration). (gardener/dashboard#1234, @petersutter)
    • You can change the default token expiration with .frontendConfig.serviceAccountDefaultTokenExpiration in the values.yaml file of the gardener-dashboard chart
    • You can change the list of the intended audiences of the service account token with .tokenRequestAudiences in the values.yaml file of the gardener-dashboard chart

✨ New Features

πŸ› Bug Fixes

  • [OPERATOR] Fixed a bug that caused seeds with empty label section not to be mapped to cloud profiles with empty matchLabels (gardener/dashboard#1236, @grolu)

πŸƒ Others

1.58.0

24 May 11:31
Compare
Choose a tag to compare

[dashboard]

πŸ› Bug Fixes

1.57.0

18 May 15:40
Compare
Choose a tag to compare

[dashboard]

⚠️ Breaking Changes

✨ New Features

πŸ› Bug Fixes

  • [OPERATOR] Terminal: Fixed issue Unable to connect to the server: x509: certificate signed by unknown authority when running a kubectl command within the terminal pod (gardener/dashboard#1207, @petersutter)

πŸƒ Others

1.56.0

16 May 12:24
Compare
Choose a tag to compare

[dashboard]

⚠️ Breaking Changes

  • [OPERATOR] The gardenctl-v2 commands that can be copied from the cluster details page to target the "Cluster" or the "Control Plane" will not include the command to set the KUBECONFIG environment variable anymore (e.g. eval $(gardenctl kubectl-env bash) in case of bash) (gardener/dashboard#1158, @petersutter)
    • A warning message is displayed when running the target command in case the KUBECONFIG environment variable does not point to the current target
    • The rc command startup script sets the KUBECONFIG variable when evaluating the command output, usually as part of the shell profile, e.g. source <(gardenctl rc bash) in case of bash. Requires gardenctl v2.1.0
    • If you do not load the gardenctl rc command in your shell profile or do not have the gk or, with bash as an example, eval "$(gardenctl kubectl-env bash)" in your bash profile, you will have to run it manually in order to have the KUBECONFIG point to the kubeconfig of the current target

✨ New Features

  • [USER] Added a warning to configure workers dialog in case additional zones require additional network configuration (gardener/dashboard#1194, @grolu)
  • [USER] Added support for Azure Private DNS (gardener/dashboard#1191, @grolu)
  • [USER] Several improvements for the readiness chips (gardener/dashboard#1190, @grolu)
    • Sort readiness chips by name
    • Left align readiness tags, this improves overview if additional chips are present for only some of the clusters
    • Fill chips that have an error state (to make them more prominent)
    • Added icons for readiness chips that have a state other than success
  • [USER] Improved worker CIDR generation for new clusters when using non default node networks (gardener/dashboard#1182, @grolu)
  • [OPERATOR] Improved visibility of user errors (gardener/dashboard#1193, @grolu)
  • [OPERATOR] Default node CIDR can be overwritten by setting the new frontend.defaultNodesCIDR value in the Dashboard configuration (gardener/dashboard#1182, @grolu)

πŸ› Bug Fixes

  • [USER] When selecting a machine image that does not support the currently selected container runtime, the Dashboard does no longer implicitly set the container runtime to something else (gardener/dashboard#1199, @grolu)
  • [USER] Fixed an issue caused by wildcard Floating IP names not mapped correctly, therefore available load balancer classes were not shown on shoot details page. Also the UI did not flag the default load balancer class (gardener/dashboard#1198, @grolu)
  • [USER] Service Accounts with more than one secret are now handled correctly (gardener/dashboard#1195, @grolu)

πŸ“– Documentation

1.55.1

04 Apr 19:30
Compare
Choose a tag to compare

[dashboard]

πŸ› Bug Fixes