-
Notifications
You must be signed in to change notification settings - Fork 40k
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
/configz doesn't work in 1.10 #61826
Comments
appreciate if anyone can try the /configz API and feedback :) |
Can you verify if the feature gate is enabled? |
@phsiao yes, still not working with the DynamicKubeletConfig on.
and dynamic-config-dir in the command line |
This url works fine for me:
Ps: |
/api/v1/proxy/nodes/${NODE_NAME}/configz/ is deprecated in 1.10. /close |
ref: |
/reopen Reopen this issue because we have to update the document. |
Fix issue: kubernetes/kubernetes#61826 Related change: kubernetes/kubernetes#59884
Fix issue: kubernetes/kubernetes#61826 Related change: kubernetes/kubernetes#59884
/close |
Fix issue: kubernetes/kubernetes#61826 Related change: kubernetes/kubernetes#59884
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
according to the Reconfigure a Node's Kubelet in a Live Cluster page, we can use /configz to fetch the whole config of kubelet. The question is, this API just reports 404 in 1.10 release which works fine in 1.8 in my setup.
What you expected to happen:
Is it not supported any more in the 1.10 release? Or just something wrong with my setup?
How to reproduce it (as minimally and precisely as possible):
try this command in this page:
curl -sSL http://localhost:8001/api/v1/proxy/nodes/${NODE_NAME}/configz
and it returns as follow:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "the server could not find the requested resource",
"reason": "NotFound",
"details": {
},
"code": 404
}
Anything else we need to know?:
Environment:
kubectl version
):Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
uname -a
):/sig node
The text was updated successfully, but these errors were encountered: