-
Notifications
You must be signed in to change notification settings - Fork 65
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
log v5 doesn't print desired log of vn-agent #183
Comments
/assign |
Have you found more information about what is going on here? |
not sure what happened , still checking |
just notice vn-agent-xxx does not exist in capn created env :( |
Yes, cause in the capn future there is two paths, CAPN w/ VC and CAPN without. CAPN w/ VC is likely going to be most folks way of deploying the architecture. |
ok, thanks for the info~ |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
I actually could reproduce this issue. Neither -v nor --v would work. 😢 |
cc @charleszheng44 did you work on the vn-agent? it looks like klog isn't configured properly with verbosity levels…? |
I will take a look. |
/assign |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
What did you expect to happen:
looks like v5 log doesn't work for detailed log
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: