Running Pods on Only Some Nodes [page]deterministic

This page demonstrates how can you run [Pods](#gloss:pod) on only some [Nodes](#gloss:node) as part of a [DaemonSet](#gloss:daemonset)

##

## Running Pods on only some Nodes

Imagine that you want to run a [DaemonSet](#gloss:daemonset), but you only need to run those daemon pods on nodes that have local solid state (SSD) storage. For example, the Pod might provide cache service to the node, and the cache is only useful when low-latency local storage is available.

### Step 1: Add labels to your nodes

Add the label `ssd=true` to the nodes which have SSDs.

```shell kubectl label nodes example-node-1 example-node-2 ssd=true ```

### Step 2: Create the manifest

Let's create a [DaemonSet](#gloss:daemonset) which will provision the daemon pods on the SSD labeled [nodes](#gloss:node) only.

Next, use a `nodeSelector` to ensure that the DaemonSet only runs Pods on nodes with the `ssd` label set to `"true"`.

### Step 3: Create the DaemonSet

Create the DaemonSet from the manifest by using `kubectl create` or `kubectl apply`

Let's label another node as `ssd=true`.

```shell kubectl label nodes example-node-3 ssd=true ```

Labelling the node automatically triggers the control plane (specifically, the DaemonSet controller) to run a new daemon pod on that node.

```shell kubectl get pods -o wide ``` The output is similar to:

``` NAME READY STATUS RESTARTS AGE IP NODE <daemonset-name><some-hash-01> 1/1 Running 0 13s ..... example-node-1 <daemonset-name><some-hash-02> 1/1 Running 0 13s ..... example-node-2 <daemonset-name><some-hash-03> 1/1 Running 0 5s ..... example-node-3 ```