Skip to content

DaemonSets

This document explains how to operate DaemonSets through kop.

Binding keys

Available shortcuts for DaemonSet-related operations are shown in the Footer area at the bottom of the page. Available actions may vary slightly by context; always use the real-time prompts in the Footer as the source of truth.

Key Action
d Delete DaemonSet
e Edit DaemonSet
r Restart DaemonSet
n Next Page
p Previous Page

Some keys are shown in the Footer only under specific conditions. For example, n and p are displayed only when the total number of resources exceeds the current screen height.

Actions

The following sections describe what each action does and how to use it.

Restart DaemonSet

Triggers a rolling restart for the selected DaemonSet.

Steps:

  1. In the left resource navigator, go to DaemonSets.
  2. Select the target DaemonSet in the list.
  3. Press r to trigger restart.
  4. Confirm the action in the prompt.
  5. Monitor Pod replacement progress on each node.

Notes:

  • Restart updates the Pod template restart annotation and performs a rolling replacement.
  • During rolling restart, old and new Pods may coexist briefly.

Edit DaemonSet

Edits the DaemonSet YAML configuration and submits changes.

Steps:

  1. In the left resource navigator, go to DaemonSets.
  2. Select the target DaemonSet in the list.
  3. Press e to open the YAML editor view.
  4. Modify the content and save to submit.

Notes:

  • Invalid or immutable field changes are rejected by the Kubernetes API.
  • If an update fails, adjust based on the error message and retry.
  • Edit DaemonSet opens in the Action Workspace. See Action Workspace for details.

Delete DaemonSet

Deletes the currently selected DaemonSet resource.

Steps:

  1. Select the target DaemonSet in the DaemonSets list.
  2. Press d to trigger deletion.
  3. Confirm the action in the prompt.

Notes:

  • Deletion removes the selected DaemonSet object from the cluster.
  • Check dependent workloads before deletion to avoid service impact.