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

[release-1.26] ensure that klog verbosity is set to the same level as logrus #7360

Conversation

thomasferrandiz
Copy link
Contributor

@thomasferrandiz thomasferrandiz commented Apr 26, 2023

Backport of #7303

Issue: #7358

@thomasferrandiz thomasferrandiz requested a review from a team as a code owner April 26, 2023 12:22
@thomasferrandiz thomasferrandiz self-assigned this Apr 26, 2023
@thomasferrandiz thomasferrandiz added this to the v1.26.5+k3s1 milestone Apr 26, 2023
@thomasferrandiz thomasferrandiz changed the title ensure that klog verbosity is set to the same level as logrus [release-1.26] ensure that klog verbosity is set to the same level as logrus Apr 26, 2023
by repeatedly settting it every second during k3s startup

Signed-off-by: Thomas Ferrandiz <[email protected]>
@thomasferrandiz thomasferrandiz force-pushed the backport-1.26-netpol-log-level branch from 81b77d5 to 0b256f0 Compare April 27, 2023 08:11
@thomasferrandiz thomasferrandiz merged commit ef0b820 into k3s-io:release-1.26 May 10, 2023
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.

2 participants