kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Clean up create-daemon-set.md

pull/49307/head
windsonsea 2025-01-07 09:41:04 +08:00
parent bac18a59ef
commit 3407a0e1cd
1 changed files with 31 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

55
content/en/docs/tasks/manage-daemon/create-daemon-set.md
View File

@ -5,7 +5,8 @@ weight: 5
---
<!-- overview -->
This page demonstrates how to build a basic {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}} that runs a Pod on every node in a Kubernetes cluster.
This page demonstrates how to build a basic {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}
that runs a Pod on every node in a Kubernetes cluster.
It covers a simple use case of mounting a file from the host, logging its contents using
an [init container](/docs/concepts/workloads/pods/init-containers/), and utilizing a pause container.
@ -13,7 +14,8 @@ an [init container](/docs/concepts/workloads/pods/init-containers/), and utilizi
{{< include "task-tutorial-prereqs.md" >}}
A Kubernetes cluster with at least two nodes (one control plane node and one worker node) to demonstrate the behavior of DaemonSets.
A Kubernetes cluster with at least two nodes (one control plane node and one worker node)
to demonstrate the behavior of DaemonSets.
## Define the DaemonSet
@ -25,41 +27,46 @@ while the main container will be a `pause` container, which keeps the Pod runnin
1. Create a DaemonSet based on the (YAML) manifest:
```shell
kubectl apply -f https://k8s.io/examples/application/basic-daemonset.yaml
```
```shell
kubectl apply -f https://k8s.io/examples/application/basic-daemonset.yaml
```
1. Once applied, you can verify that the DaemonSet is running a Pod on every node in the cluster:
```shell
kubectl get pods -o wide
```
```shell
kubectl get pods -o wide
```
The output will list one Pod per node, similar to:
The output will list one Pod per node, similar to:
```
NAME READY STATUS RESTARTS AGE IP NODE
example-daemonset-xxxxx 1/1 Running 0 5m x.x.x.x node-1
example-daemonset-yyyyy 1/1 Running 0 5m x.x.x.x node-2
```
```
NAME READY STATUS RESTARTS AGE IP NODE
example-daemonset-xxxxx 1/1 Running 0 5m x.x.x.x node-1
example-daemonset-yyyyy 1/1 Running 0 5m x.x.x.x node-2
```
1. You can inspect the contents of the logged `/etc/machine-id` file by checking the log directory mounted from the host:
1. You can inspect the contents of the logged `/etc/machine-id` file by checking
the log directory mounted from the host:
```shell
kubectl exec <pod-name> -- cat /var/log/machine-id.log
```
Where `<pod-name>` is the name of one of your Pods.
```shell
kubectl exec <pod-name> -- cat /var/log/machine-id.log
```
Where `<pod-name>` is the name of one of your Pods.
## {{% heading "cleanup" %}}
```
kubectl delete --cascade=foreground --ignore-not-found --now daemonsets/example-daemonset
```
To delete the DaemonSet, run this command:
```shell
kubectl delete --cascade=foreground --ignore-not-found --now daemonsets/example-daemonset
```
This simple DaemonSet example introduces key components like init containers and host path volumes,
which can be expanded upon for more advanced use cases. For more details refer to
[DaemonSet](/docs/concepts/workloads/controllers/daemonset/).
## {{% heading "whatsnext" %}}
* See [Performing a rolling update on a DaemonSet](/docs/tasks/manage-daemon/update-daemon-set/)
* See [Creating a DaemonSet to adopt existing DaemonSet pods](/docs/concepts/workloads/controllers/daemonset/)