-
Notifications
You must be signed in to change notification settings - Fork 8.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
Feature request: kubectl plugin #3755
Comments
|
True. Wouldn't want to annoy https://github.com/nginxinc/kubernetes-ingress :-) |
|
we should use https://github.com/GoogleContainerTools/krew to package the plugin |
@alexkursell some time ago I wrote this https://gist.github.com/aledbf/db25dbc723fc7d71345a9657abfd766d as an idea for the cli/plugin |
That seems like a great set of features to add! Although how is the configuration different between cloud providers? I'd expect the configuration to be the same since it's all kubernetes. |
In AWS you can choose between different load balancers, ELBs in L4/L7 or NLBs, also enabling proxy protocol or not. |
Now that #3686 is merged, we should do as @aledbf suggested and write a kubectl plugin to make debugging even easier.
Currently, here are the steps to inspecting some backend information:
kubectl get pods -n <NAMESPACE> | grep ingress
or similar to get a running podkubectl exec -n <NAMESPACE> <POD NAME> -- /dbg backends list
By adding a kubectl plugin that takes care of finding and
exec
ing into the right pod, this could be reduced to something like:kubectl nginx -n <NAMESPACE> backends list
Making a kubectl plugin would also allow us to do things like getting and diffing the configuration from multiple pods in a deployment, or maybe finding and printing ingress resource definitions for a given backend.
Some questions for discussion:
cc: @ElvinEfendi, @aledbf
The text was updated successfully, but these errors were encountered: