-
Notifications
You must be signed in to change notification settings - Fork 112
Update consul-k8s cli proxy command docs #1309
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
base: main
Are you sure you want to change the base?
Conversation
Vercel Previews Deployed
|
Broken Link CheckerNo broken links found! 🎉 |
aimeeu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some suggestions so that the text follows the Education style guide. Thanks!
content/consul/v1.22.x/content/docs/reference/cli/consul-k8s.mdx
Outdated
Show resolved
Hide resolved
| | Flag | Description | Default | | ||
| | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | ||
| | <nobr>`-namespace`, `-n`</nobr> | `String` Specifies the namespace containing the target Pod. | Current [kubeconfig](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) namespace. | | ||
| | <nobr>`-update-level`, `-u`</nobr> | `String` Specifies the logger (optional) and the level to update. <p>Use the following format to configure the same level for loggers: `-update-level <LEVEL>`.</p> <p>You can also specify a comma-delineated list to configure levels for specific loggers, for example: `-update-level grpc:warning,http:info`.</p> | none | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | <nobr>`-update-level`, `-u`</nobr> | `String` Specifies the logger (optional) and the level to update. <p>Use the following format to configure the same level for loggers: `-update-level <LEVEL>`.</p> <p>You can also specify a comma-delineated list to configure levels for specific loggers, for example: `-update-level grpc:warning,http:info`.</p> | none | | |
| | <nobr>`-update-level`, `-u`</nobr> | `String` Specifies the optional logger and the level to update. <p>Use the following format to configure the same level for loggers: `-update-level <LEVEL>`.</p> <p>You can also specify a comma-delimited list to configure levels for specific loggers, such as `-update-level grpc:warning,http:info`.</p> | none | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Specifies the logger (optional) and the level to update." the statement makes more sense as it try to convey that logger is an optional field but the level to update is mandatory field for update-level flag.. this is what command intends to expect.
So i guess.. this part is fine and keeping as it is.
content/consul/v1.22.x/content/docs/reference/cli/consul-k8s.mdx
Outdated
Show resolved
Hide resolved
content/consul/v1.22.x/content/docs/reference/cli/consul-k8s.mdx
Outdated
Show resolved
Hide resolved
content/consul/v1.22.x/content/docs/reference/cli/consul-k8s.mdx
Outdated
Show resolved
Hide resolved
19ca0a3 to
1052cd1
Compare
Docs change for PR: https://github.com/hashicorp/consul-k8s/pull/4788/
Changes:
Added -capture flag to
proxy logcommand.This will enable user to capture log for given duration and write them to a file in current working dir.
If -update-level flag is provided along with -capture flag, it will set given new log level, capture the log for given duration and reset the log level to existing one post log capture.
Sample command:
consul-k8s proxy log <podname> -capture 1m -update-level debug