-
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
Using --v=3 does not return valid json for config #12330
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
% k -n ingress-nginx get po ingress-nginx-controller-7d978dd4c-kjhtj -v=8 |
What happened:
To debug a configuration issue I added
--v=3
to the pod to get the used configuration.What you expected to happen:
According to the docs (https://kubernetes.github.io/ingress-nginx/troubleshooting/#debug-logging) the output should be in json format.
The output it not valid json.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): 1.11.3
Snippet of my output:
I mean the bunch of
\
would be easy to fix but it seems it just dump a k8s object. Unfortunately there are things like labels in there that I don't think belong to the nginx config iteself and then there is thelast-applied-configuration
which is embedded json and maybe this breaks it.Would be nice to get an easy way to debug the config.
How to reproduce this issue:
Use
--v=3
Anything else we need to know:
The resulting config is around 2k lines with a bunch of hosts so it's hard to format by hand
The text was updated successfully, but these errors were encountered: