![]() Since a lot of Kubernetes clusters are now being hosted in your cloud provider of choice, those master logs are a little bit trickier to get to. You can also use one of the many different logging consoles or aggregation services out there. Depending on where you’re hosting the machine, you may have to SSH into the node directly. These logs sadly can’t be looked at through the kubectl command but instead need to be looked at directly from the machine. These logs tell you what’s going on and what can be helpful in troubleshooting problems with the master node. /var/log/kube-proxy.log– Kube Proxy, responsible for service load balancing./var/log/kubelet.log– Kubelet, responsible for running containers on the node.These are the two log files you can look at on worker nodes: /var/log/kube-controller-manager.log – Controller that manages replication controllers./var/log/kube-scheduler.log– Scheduler, responsible for making scheduling decisions./var/log/kube-apiserver.log– API Server, responsible for serving the API.There are three log files you can look at in the master node: The Kubernetes master controls the entire cluster-what’s running where and what needs to be provisioned-in coordination with the worker nodes. The first thing you may want to look at is how the Kubernetes master and nodes are behaving. In this blog post, you’ll learn how to review logs from Kubernetes and what you may want to be running in it. Let’s make sure you know how to see what’s going on inside.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |