[dashboard]

Action Required

• [OPERATOR] ⚠️ This Dashboard version is not compatible with Gardener versions prior 0.14.x (#274, @grolu)

Most notable changes

• [USER] Improved search in cluster list: You can now search for name, project, infrastructure, created by, purpose, Kubernetes version and journal labels (#276, @grolu)
• [USER] Introduced client-side paging on the "all projects" list to improve rendering performance of large cluster lists (#276, @grolu)
• [OPERATOR] Added support for Alibaba Cloud (#273, @holgerkoser)

Improvements

• [USER] The cluster name on the details page is shown in the breadcrumb (#281, @petersutter)
• [USER] Fixed: Sort by version in cluster list (#276, @grolu)
• [USER] Fixed: Readiness tag issues (#276, @grolu)
  • Cursor pointer did not work due to latest Vuetify updates
  • Always use shortened name for readiness tags
  • Show full name as tooltip
• [USER] Fixed: Namespace instead of real project name was shown in "all projects" cluster list (#276, @grolu)
• [USER] Fixed: Some alignment issues in help and about menu (#276, @grolu)
• [USER] Fixed an issue that could cause popovers to be placed behind main menu (#271, @grolu)
• [USER] It is possible to disable jkws certificate checking via helm values now (#269, @eaterm)
• [OPERATOR] Show Gardener API version in Gardener Dashboard (#289, @grolu)
• [OPERATOR] Added the ability to add custom ingress annotations in helm chart (#288, @eaterm)
• [OPERATOR] Updated vuetify to 1.4.2 (#287, @petersutter)
• [OPERATOR] Kibana ingress has been added to Cluster Details page (#286, @ialidzhikov)
• [OPERATOR] Fixed: General information banner did not appear anymore (#283, @grolu)
• [OPERATOR] Show warning if deleting a cluster for which reconciliation is deactivated (#275, @grolu)
• [OPERATOR] Progressing conditions are displayed in blue color (operator/admin only) (#274, @grolu)
• [OPERATOR] It is now possible to show clusters with condition(s) state progressing in "all clusters with issues" list (#274, @grolu)
• [OPERATOR] Support for OIDC provider that does not allow CORS on the metadata endpoint (#270, @holgerkoser)
• [OPERATOR] It is possible to configure the frontend oidc-client via helm values now. (#268, @holgerkoser)