Difference between revisions of "Kubelet"
Jump to navigation
Jump to search
| (44 intermediate revisions by 4 users not shown) | |||
| Line 2: | Line 2: | ||
<code>kubelet</code> process in [[Kubernetes]] is responsible for running containers on the node | <code>kubelet</code> process in [[Kubernetes]] is responsible for running containers on the node | ||
* Configuration: <code>[[/etc/kubernetes/kubelet.conf]]</code> | * Configuration: <code>[[/etc/kubernetes/kubelet.conf]]</code> | ||
| − | * Logs: <code>[[/var/log/kubelet.log]]</code> | + | * GitHub: https://github.com/openshift/origin/tree/master/vendor/k8s.io/kubernetes/pkg/kubelet |
| + | * Logs: | ||
| + | ** <code>[[/var/log/kubelet.log]]</code> | ||
| + | ** [[GKE]]: <code>[[gcloud logging read projects/your-project/logs/kubelet]]</code> | ||
* Port: <code>kubelet</code> listen on [[List of TCP ports|port 10250]] | * Port: <code>kubelet</code> listen on [[List of TCP ports|port 10250]] | ||
* Installation Ubuntu: <code>[[snap install kubelet --classic]]</code> (<code>[[snap stop]] kubelet.daemon</code> or <code>[[snap start]] kubelet.daemon</code>) | * Installation Ubuntu: <code>[[snap install kubelet --classic]]</code> (<code>[[snap stop]] kubelet.daemon</code> or <code>[[snap start]] kubelet.daemon</code>) | ||
| + | * [[Kubelet logs]]: [[docker logs kubelet]] | ||
== Commands == | == Commands == | ||
[[systemctl start]] snap.kubelet.daemon.service | [[systemctl start]] snap.kubelet.daemon.service | ||
[[systemctl stop]] snap.kubelet.daemon.service | [[systemctl stop]] snap.kubelet.daemon.service | ||
| − | |||
[[snap start]] [[kubelet]].daemon | [[snap start]] [[kubelet]].daemon | ||
| Line 19: | Line 22: | ||
The [[Container Network Interface (CNI)]] plugin is selected by passing <code>[[kubelet]]</code> the <code>--network-plugin=cni</code> | The [[Container Network Interface (CNI)]] plugin is selected by passing <code>[[kubelet]]</code> the <code>--network-plugin=cni</code> | ||
| − | + | == Errors == | |
| − | + | * <code>[[The kubelet on the node ip-123.123.123.123 is not healthy]]</code> | |
| − | |||
== Related terms == | == Related terms == | ||
| + | * [[Pod Lifecycle Event Generator (PLEG)]] | ||
* Liveness probe: (<code>[[livenessProbe]]</code>) | * Liveness probe: (<code>[[livenessProbe]]</code>) | ||
* Readiness probe: (<code>[[readinessProbe]]</code>) | * Readiness probe: (<code>[[readinessProbe]]</code>) | ||
| Line 30: | Line 33: | ||
* [[Kubelet Container Runtime Interface (CRI)]] | * [[Kubelet Container Runtime Interface (CRI)]] | ||
* <code>[[systemctl status kubelet]]</code> | * <code>[[systemctl status kubelet]]</code> | ||
| + | * <code>[[gcloud logging read]] projects/yourproject/logs/kubelet</code> | ||
| + | * [[Kubernetes controller manager]] | ||
| + | * <code>[[Conditions:]]</code> <code>[[kubelet is posting ready status. AppArmor enabled]]</code> | ||
| + | * <code>[[--kubelet-insecure-tls]]</code> | ||
| + | * [[Kubelet conditions]]: <code>[[MemoryPressure]]</code> | ||
| + | * <code>[[Node-pressure Eviction]]</code> | ||
| + | * <code>[[kubectl get events]] [[Starting kubelet]]</code> | ||
| + | * <code>[[cloud-node-lifecycle-controller]]</code> | ||
| + | * <code>[[kind: KubeletConfiguration]]</code> | ||
| + | * <code>[[oom_score_adj]]</code> | ||
| + | * [[Kubelet stopped posting node status.]] | ||
| + | * [[DNSConfigForming kubelet warning]] | ||
| + | * [[Kubelet Resource Metrics Endpoint]] | ||
| + | * <code>[[Scheduled]], [[Pulling]], [[Pulled]], [[Created]], [[Started]], [[Unhealthy]], [[Killing]]</code> | ||
== Activities == | == Activities == | ||
| Line 35: | Line 52: | ||
== News == | == News == | ||
| − | * 05/2022 [[Kubernetes 1.24]]: | + | * 05/2022 [[Kubernetes 1.24]]: [[Dockershim removed from kubelet]] |
== See also == | == See also == | ||
* {{kubelet}} | * {{kubelet}} | ||
* {{Kubernetes components}} | * {{Kubernetes components}} | ||
| − | |||
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Latest revision as of 09:42, 1 May 2024
kubelet process in Kubernetes is responsible for running containers on the node
- Configuration:
/etc/kubernetes/kubelet.conf - GitHub: https://github.com/openshift/origin/tree/master/vendor/k8s.io/kubernetes/pkg/kubelet
- Logs:
- Port:
kubeletlisten on port 10250
- Installation Ubuntu:
snap install kubelet --classic(snap stop kubelet.daemonorsnap start kubelet.daemon) - Kubelet logs: docker logs kubelet
Commands[edit]
systemctl start snap.kubelet.daemon.service systemctl stop snap.kubelet.daemon.service
snap start kubelet.daemon Started. systemctl status snap.kubelet.daemon.service
Networking[edit]
The Container Network Interface (CNI) plugin is selected by passing kubelet the --network-plugin=cni
Errors[edit]
Related terms[edit]
- Pod Lifecycle Event Generator (PLEG)
- Liveness probe: (
livenessProbe) - Readiness probe: (
readinessProbe) systemctl stop snap.kubelet.daemon.servicekubectl describe pods | grep Unhealthy- Kubelet Container Runtime Interface (CRI)
systemctl status kubeletgcloud logging read projects/yourproject/logs/kubelet- Kubernetes controller manager
Conditions:kubelet is posting ready status. AppArmor enabled--kubelet-insecure-tls- Kubelet conditions:
MemoryPressure Node-pressure Evictionkubectl get events Starting kubeletcloud-node-lifecycle-controllerkind: KubeletConfigurationoom_score_adj- Kubelet stopped posting node status.
- DNSConfigForming kubelet warning
- Kubelet Resource Metrics Endpoint
Scheduled, Pulling, Pulled, Created, Started, Unhealthy, Killing
Activities[edit]
News[edit]
See also[edit]
kubelet, Pod Lifecycle Event Generator (PLEG), Kubelet conditions,/etc/kubernetes/kubelet.conf, /var/log/kubelet.log, Kubelet Container Runtime Interface (CRI),crictl,context deadline exceeded, E1122, E1124, Starting kubelet, NodeHasDiskPressure, NodeHasInsufficientMemory, rebooted, Node-pressure Eviction, Kubelet logs,manager: kubelet- Kubernetes Components,
kube-proxy, kube-scheduler, kube-apiserver, kubelet, kubectl, kubeadm, Kubernetes controller manager, Kubernetes controllers, Kubernetes Addons, Kubernetes Topology Manager
Advertising:
