-
Notifications
You must be signed in to change notification settings - Fork 39.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dashboard version to v1.8.3 #57326
Conversation
/assign @jbeda |
Is there a way to check logs of a container that is failing? Without that it is hard to debug. |
@floreks Would it be possible to update this PR to go straight to a 1.8.3 as per kubernetes/dashboard#2813 ? |
@@ -7,10 +7,6 @@ metadata: | |||
name: kubernetes-dashboard-minimal | |||
namespace: kube-system | |||
rules: | |||
# Allow Dashboard to create 'kubernetes-dashboard-key-holder' secret. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for this change, probably need to add an empty EnsureExists kubernetes-dashboard-key-holder
Secret to the secrets.yaml file
@@ -30,7 +30,7 @@ spec: | |||
priorityClassName: system-cluster-critical | |||
containers: | |||
- name: kubernetes-dashboard | |||
image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.0 | |||
image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you also change the kubernetes-dashboard-certs volume back to a secret (reverting the dashboard change in
https://github.com/kubernetes/kubernetes/pull/58720/files#diff-7ab88bb7654d97946d6328f11f29d177, now that the dashboard only reads from that mount)
@liggitt Done. |
/lgtm |
needs squashing |
/approve Please cleanup history. |
a6463a5
to
c102839
Compare
c102839
to
85a537c
Compare
@mikedanese rebased and squashed the commits. |
/hold cancel |
@liggitt could you take a look? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floreks, liggitt, mikedanese The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
@floreks: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/test pull-kubernetes-unit |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
…720-#57326-#60342-upstream-release-1.8 Automatic merge from submit-queue. [1.8] Automated cherry pick of #58720 #57326 #60342 Cherry pick of #58720 #57326 #60342 on release-1.8. #58720: Ensure that the runtime mounts RO volumes read-only #57326: Update Dashboard version to v1.8.3 #60342: Fix nested volume mounts for read-only API data volumes Note for reviewers: The Dashboard update is necessary because previous versions of the Dashboard attempted to write to the secret volume on startup, and so the read-only secret volume change prevented the Dashboard from starting. ```release-note Update dashboard version to v1.8.3 Containers now mount secret, configMap, downwardAPI and projected volumes read-only. Previously, container modifications to files in these types of volumes were temporary and reverted by the kubelet during volume sync. Until version 1.11, setting the feature gate ReadOnlyAPIDataVolumes=false will preserve the old behavior. ```
…720-upstream-release-1.9 Automatic merge from submit-queue. [1.9] Automated cherry pick of #58720 #57326 #60342 Cherry pick of #58720 #57326 #60342 on release-1.9. #58720: Ensure that the runtime mounts RO volumes read-only #57326: Update Dashboard version to v1.8.3 #60342: Fix nested volume mounts for read-only API data volumes Note for reviewers: The Dashboard update is necessary because previous versions of the Dashboard attempted to write to the secret volume on startup, and so the read-only secret volume change prevented the Dashboard from starting. ```release-note Changes secret, configMap, downwardAPI and projected volumes to mount read-only, instead of allowing applications to write data and then reverting it automatically. Until version 1.11, setting the feature gate ReadOnlyAPIDataVolumes=false will preserve the old behavior. Updates dashboard version to v1.8.3 to avoid writing to read-only locations. ```
What this PR does / why we need it: Updates dashboard addon to the latest version. Changelog can be found here.
Release note: