This repository has been archived by the owner on Nov 15, 2022. It is now read-only.
chore(deps): update dependency gardener/dashboard to v1.63.0 (latest-3) #443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.61.3
->1.63.0
Release Notes
gardener/dashboard
v1.63.0
Compare Source
[dashboard]
✨ New Features
dashboard-webterminal
service account is now cleaned up for new terminals if it is not referenced anymore by any webterminal session. (gardener/dashboard#1309, @petersutter)🐛 Bug Fixes
garden
cluster terminal could not be successfully started if thedashboard-webterminal
does not have the required permissions (ref #1268) (gardener/dashboard#1309, @petersutter)v1.62.0
Compare Source
[dashboard]
gardener-dashboard
Helm chart has been split into two different subcharts (runtime
andapplication
). This change required that all chart values that previously were on top-level have now moved under the.global
key. However, the structure/types of all existing keys has not changed. Please check thevalues.yaml
. (gardener/dashboard#1283, @petersutter)✨ New Features
yaml
tab tooverview
Target Cluster
command is now shown for users withcreate
shoots/adminkubeconfig
permission (e.g. for users having theadmin
project role). Previously this was only shown for gardener admins. (gardener/dashboard#1300, @petersutter)gardener-dashboard
Helm chart now supports configuration for enabling service account token volume projection. It is exposed through the.Values.global.serviceAccountTokenVolumeProjection
section in thevalues.yaml
file. (gardener/dashboard#1283, @petersutter)User
instead of aServiceAccount
subject in theClusterRoleBinding
for the Gardener Dashboard when using virtual garden setup by setting.Values.global.virtualGarden.userName
in thevalues.yaml
file. (gardener/dashboard#1283, @petersutter)controllerregistration
resource using theapp.kubernetes.io/version
label. The dashboard will show the defined version in the about dialog (gardener/dashboard#1291, @grolu)id_token
lifetimes. (gardener/dashboard#1297, @holgerkoser)client_secret
. (gardener/dashboard#1297, @holgerkoser)🐛 Bug Fixes
kube-apiserver
watches. Due to this bug the list did not get any realtime updates and the dashboard pod had to be manually restarted. (gardener/dashboard#1326, @holgerkoser)text/plain
whereapplication/json
is expected an error message likeUnexpected token x in JSON at position y
could be seen in the logs. You are now able to see what the actual server response was (gardener/dashboard#1330, @holgerkoser)🏃 Others
gardenctl
version selection now moved to the newly introducedSettings
page which can be found in the menu of your avatar. (gardener/dashboard#1297, @holgerkoser)deletionTimestamp
is set) (gardener/dashboard#1307, @petersutter)gardener-dashboard
user is no longer bound to thecluster-admin
ClusterRole
. Instead, it is bound to the newly introducedgardener.cloud:system:dashboard
ClusterRole
, which grants only those permissions that are required for the dashboard user. (gardener/dashboard#1283, @petersutter)spec.secretRef
is not required anymore ifSeed
is aManagedSeed
(gardener/dashboard#1312, @petersutter)v2.35.3-distroless
(gardener/dashboard#1317, @petersutter)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.