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

Increase log level for Kubernetes components #4111

Closed
mimowo opened this issue Jan 30, 2025 · 2 comments · Fixed by #4095
Closed

Increase log level for Kubernetes components #4111

mimowo opened this issue Jan 30, 2025 · 2 comments · Fixed by #4095
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@mimowo
Copy link
Contributor

mimowo commented Jan 30, 2025

What would you like to be added:

Increasing log-level for Kubernetes componets (including Kubelet) to V(3).

The effort is started in PR: #4095

Why is this needed:

Having more logs from K8s components could be helpful for investigations of flakes as discussed in #4056 (comment).

I also think that with tighter integration between kueue and kubernetes (like in TAS) the logs will be helpful to investigate some rare failures.

Also, any additional logs will be helpful for complex features like MultiKueue.

@mimowo mimowo added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 30, 2025
@mimowo
Copy link
Contributor Author

mimowo commented Jan 30, 2025

/remove-kind feature
/kind cleanup

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Jan 30, 2025
@mimowo
Copy link
Contributor Author

mimowo commented Jan 30, 2025

cc @mbobrovskyi @PBundyra

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants