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

doc(kic) remove stderrthreshold flag #2835

Closed
wants to merge 1 commit into from
Closed

Conversation

rainest
Copy link
Contributor

@rainest rainest commented May 10, 2021

Summary

Remove the --stderrthreshold flag from KIC documentation. This is a leftover from an old logging library we used prior to 0.10.0. It hasn't actually been available since.

Reason

Found when reviewing log flag updates for KIC 2.0: Kong/kubernetes-ingress-controller#1294 (review)

Remove the --stderrthreshold flag from KIC documentation. This is a
leftover from an old logging library we used prior to 0.10.0. It hasn't
actually been available since.
@rainest rainest requested a review from a team as a code owner May 10, 2021 18:19
@netlify
Copy link

netlify bot commented May 10, 2021

Deploy preview for kongdocs ready!

Built with commit 3a2fdb6

https://deploy-preview-2835--kongdocs.netlify.app

@mflendrich
Copy link
Member

It appears that the k8s api machinery does use this flag, and it's being registered using a separate unrelated mechanism.
In fact there's a bug in Railgun that cobra doesn't register that flag with the root command.

So I think that the appropriate fix here is not to remove this flag from the documentation, but to ensure that this flag works in Railgun.

@rainest
Copy link
Contributor Author

rainest commented May 10, 2021

Aight, nevermind then. Kong/kubernetes-ingress-controller#1297 instead.

@rainest rainest closed this May 10, 2021
@rainest rainest deleted the fix/remove-old-kic-flag branch May 10, 2021 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants