-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Kubectl Proxy to Dashboard broken in 1.7.6 #52729
Comments
@discostur
Note: Method 1 will trigger an email to the group. You can find the group list here and label list here. |
I have the same problem |
Same issue here, the fact is if I add a trailing "/" to the following url, the dashboard will show. |
@kubernetes/sig-network-bugs |
@TomskDiver: Reiterating the mentions to trigger a notification: In response to this:
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. |
/remove-sig network /sig cli |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.. Preserve leading and trailing slashes on proxy subpaths subresource parsing was not populating path parameters correctly (leading and trailing slashes were being stripped) this caused bad locations to be sent to the proxy, causing #52022. the first attempt to fix that (#52065) unconditionally prefixed '/', which broke the redirect case (#52813 #52729) fixes #52813, fixes #52729 needs to be picked to 1.7 and 1.8 ```release-note Restores redirect behavior for proxy subresources ```
For anyone running into this issue with v1.8.0, see this link, and if you're using the proxy, try:
|
the wiki page has been removed. How can i see the link? |
/kind bug
What happened:
Deployed a new cluster v1.7.6 with kubeadm and tried to access dashboard via kubectl proxy. I tested two links, but only one works:
What you expected to happen:
Should work, because with kubernetes 1.7.5 it works without any problem.
How to reproduce it (as minimally and precisely as possible):
deploy new cluster 1.7.6 with kubeadm (centos 7.4) and calico network provider
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):Already discussed the problem at the dashboard repository and it seems to be a problem with kube proxy
kubernetes/dashboard#2368
The text was updated successfully, but these errors were encountered: