Deckhouse CLI (d8)
D8 - Deckhouse CLI
The d8 command-line client for Deckhouse Kubernetes Platform: cluster status, modules, backups, mirroring and diagnostics
- 21 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The install script downloads and installs a binary
- Commands need cluster access and can change configuration, modules and users
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/d8-deckhouse-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The install script downloads and installs a binary
- Commands need cluster access and can change configuration, modules and users
This is third-party code. Review the repository files before installing.
What it does
d8 manages Deckhouse Kubernetes Platform clusters from the terminal. Its commands cover etcd snapshots and configuration backups, container registry operations, module mirroring for air-gapped setups, a cluster status report and debug archive collection. It also handles Dex user operations such as password and 2FA reset, lock and unlock. An agent can call d8 through the shell to gather cluster status or diagnostics.
Who it is for. DevOps engineers and administrators running clusters on Deckhouse.
Good fit when
- You need a quick read-only health report of a Deckhouse cluster via d8 status
- You are preparing a mirror of modules and images for an air-gapped environment
- You collect a debug archive or controller logs to investigate an incident
- You automate etcd and configuration backups in CI/CD
Not a fit when
- The cluster does not run Deckhouse: plain Kubernetes is served by kubectl and helm
- You are not ready to give the agent a kubeconfig with admin rights
Example request
Run d8 status and briefly list cluster problems: nodes, Deckhouse pods, alertsLimitations
Works only with Deckhouse Kubernetes Platform. Building from source requires access to private repositories. Binaries are provided for Linux, macOS and Windows (amd64, plus arm64 for Linux and macOS).
How to disable. Remove the d8 binary from PATH or deny the d8 command in the agent's permission settings.
FAQ
How do I get automatic updates?
The README recommends installing d8 via trdl, which supports release channels and automatic updates.
Does d8 status change anything in the cluster?
No, the README describes it as a read-only snapshot: nodes, Deckhouse pods, releases, edition, settings, registry, alerts, CNI and queue.
Discussion
No questions or reviews yet.
Related
CLI toolsAn open-source Kubernetes UI with a built-in MCP server: the agent inspects the cluster, diagnoses breakages and operates it with RBAC in mind
KubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
Kubernetes MCP
MCP Server Kubernetes
MCP server for managing a Kubernetes cluster through kubectl and Helm, with a non-destructive mode
An MCP server and skills on top of Kubernetes network observability: an agent investigates incidents and queries cluster traffic through an eBPF-built index
CLI for full-cycle CI/CD to Kubernetes: image builds, Helm-based deploys and container registry cleanup
MCP server for Kubernetes: the agent reads cluster state, diagnoses pod failures and runs operations through kubectl
README in short
D8 is the command-line client for Deckhouse Kubernetes Platform. Its main commands are backup, cr, mirror, status, system and user-operation. It can be installed with a script, a binary from GitHub Releases or via trdl. Building from source uses Task and requires access to private dependencies.