Skip to content
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

kube-proxy reference showing wrong logging flags #44750

Open
manuelbuil opened this issue Jan 15, 2024 · 8 comments
Open

kube-proxy reference showing wrong logging flags #44750

manuelbuil opened this issue Jan 15, 2024 · 8 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. language/en Issues or PRs related to English language priority/backlog Higher priority than priority/awaiting-more-evidence. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@manuelbuil
Copy link
Contributor

manuelbuil commented Jan 15, 2024

Hi,

By grepping on the logging related kube-proxy flags, I see:

* log-flush-frequency
* log-json-info-buffer-size
* log-json-split-stream
* logging-format

However, in the reference docs there are many more:

* alsologtostderr
* log_backtrace_at 
* log_dir
* log_file
* log_file_max_size
* logtostderr

If I use any of those, as expected, I get an error: Error: unknown flag:

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 15, 2024
@sftim
Copy link
Contributor

sftim commented Jan 15, 2024

/kind bug
/sig docs
/language en

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. sig/docs Categorizes an issue or PR as relevant to SIG Docs. language/en Issues or PRs related to English language labels Jan 15, 2024
@sftim
Copy link
Contributor

sftim commented Jan 15, 2024

/triage accepted
/priority backlog

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 15, 2024
@kundan2707
Copy link
Contributor

/assign

@k8s-ci-robot
Copy link
Contributor

@kundan2707: The label(s) sig/netwotk cannot be applied, because the repository doesn't have them.

In response to this:

/sig netwotk

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.

@kundan2707
Copy link
Contributor

/sig network

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Jul 2, 2024
@mengjiao-liu
Copy link
Member

mengjiao-liu commented Jul 4, 2024

@kundan2707
Copy link
Contributor

@mengjiao-liu i have considered removed flag too and updated as per latest available flags

@mengjiao-liu
Copy link
Member

Great! the above information is for reference only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. language/en Issues or PRs related to English language priority/backlog Higher priority than priority/awaiting-more-evidence. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants