AKS
AKS copied to clipboard
Azure
[Getting this error when running kubectl exec error: unable to upgrade connection: Authorization error (user=masterclient, verb=create, resource=nodes, subresource=proxy)]
Describe the bug Getting this error when running kubectl exec error: unable to upgrade connection: Authorization error (user=masterclient, verb=create, resource=nodes, subresource=proxy)] when running the belwo command
kubectl exec -it -n nginx-ingress nginx-ingress-controller-64bf68d79b-4sdwg -- /nginx-ingress-controller --version
To Reproduce Steps to reproduce the behavior:
- kubectl exec -it -n nginx-ingress nginx-ingress-controller-64bf68d79b-4sdwg -- /nginx-ingress-controller --version
- Unable to use a TTY - input is not a terminal or the right kind of file error: unable to upgrade connection: Authorization error (user=masterclient, verb=create, resource=nodes, subresource=proxy)
Expected behavior give the nginx version in the inside the POD
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:16:20Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"windows/amd64"} Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.19", GitCommit:"ea947be6fad5815bceb695a65a988759a30cda91", GitTreeState:"clean", BuildDate:"2021-05-25T01:16:51Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"} WARNING: version difference between client (1.23) and server (1.18) exceeds the supported minor version skew of +/-1
Additional context Its the Azure AKS cluster using the local RBAC, all other clusters with same configuration are fine except this one
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @deepak1185 do you still experience such error in your cluster?
This issue will now be closed because it hasn't had any activity for 7 days after stale. deepak1185 feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.