Add support for standard kubectl tracing#217
Open
skissane-medallia wants to merge 2 commits intokubecost:mainfrom
Open
Add support for standard kubectl tracing#217skissane-medallia wants to merge 2 commits intokubecost:mainfrom
skissane-medallia wants to merge 2 commits intokubecost:mainfrom
Conversation
I am having a problem with the portforwarding into the pod. Standard approach for debugging these kinds of issues is to pass `-v=9` argument to `kubectl` so I see the actual API traffic dumps in the logs. But `kubectl cost` doesn't support that argument, so there is no way to turn the K8S API client library tracing on. Hence, I have added support for those arguments.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Add support for enabling K8S API client library tracing
Does this PR rely on any other PRs?
No
How does this PR impact users? (This is the kind of thing that goes in release notes!)
I am having a problem with the portforwarding into the pod. Standard approach for debugging these kinds of issues is to pass
-v=9argument tokubectlso I see the actual API traffic dumps in the logs. Butkubectl costdidn't support that argument, so there was no way to turn the K8S API client library tracing on.Links to Issues or ZD tickets this PR addresses or fixes
None
How was this PR tested?
kubectl cost namespace -v=9shows K8S API traffic, for example:Have you made an update to documentation?
No