Using Talos Linux to set up static pods in Kubernetes.
kubelet
bypassing the Kubernetes API server checks and validations.
Most of the time DaemonSet
is a better alternative to static pods, but some workloads need to run
before the Kubernetes API server is available or might need to bypass security restrictions imposed by the API server.
See Kubernetes documentation for more information on static pods.
kubelet
using a local HTTP server, kubelet
picks up the definition and launches the pod.
Talos accepts changes to the static pod configuration without a reboot.
To see a full list of static pods, use talosctl get staticpods
, and to see the status of the static pods (as reported by the kubelet
), use talosctl get staticpodstatus
.
kubectl get pods
, logs can be retrieved with kubectl logs
, etc.
talosctl containers --kubernetes
:
talosctl logs --kubernetes
:
kubelet
logs (talosctl logs kubelet
) to find the problem:
StaticPod
resources combined with Talos-generated control plane static pods:
<namespace>-<name>
to the static pods specified in the machine configuration.
On control plane nodes status of the running static pods is available in the StaticPodStatus
resource: