-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Logging of kube-scheduler #10533
Comments
K3s runs all the Kubernetes components in the main k3s process, so their logs are all mixed together in the k3s journald log. |
I tried looking for kube-scheduler using k3s journald with v=10 set for entire server configuration. However, I am not able to see any logs |
It's all in there together. It can be hard to tell which logs are from what component, since they don't have anything uniquely identifying the source. If you can't see ANY logs then you're probably not looking in the right place... |
Are logs from k8s default scheduler by default imported to k3s component logging as well ? |
We don't import anything. They just all run in one process, and are output to stdout/stderr same as everything else. If you're running k3s under systemd, they go in the journald log. |
Can someone direct me to the steps to view the logs of default kube-scheduler in k3s ?
The text was updated successfully, but these errors were encountered: