shdctl global flags and command reference
Find the global flags and commands you can use to deploy and manage Self-Hosted Deployment releases with shdctl.
Read time 3 minutesLast updated a day ago
Find a command for a task
shdctl has one required operation: , which renders Helm chart values from your file. Your CI, GitOps controller, or operator workflow can replace every other operation.
shdctl release generatemanifest.yamlTask | Command |
|---|---|
| Render Helm charts from the manifest (required). | |
| Check that the cluster meets the prerequisites. | |
| Pull the release archive from the Unity registry. | |
| Mirror images and ORAS artifacts to your registry. | |
| Check that your registry holds what the manifest needs. | |
| Render Kubernetes Secret manifests. | |
| Apply secrets to the cluster. | |
| Rebuild the secrets import file from a running cluster. | |
| Deploy charts with Helm or ArgoCD. | |
For the recommended CI and ArgoCD pipeline, and other ways to combine these operations, refer to Workflows.
Command summary
Command | Description |
|---|---|
| Print the version number. |
| Set registry credentials (interactive). |
| View configuration. |
| Set registry credentials. Prompts on a terminal. For CI, use |
| Delete registry credentials. |
| Initialize a new manifest file interactively. |
| Validate a manifest file against the CUE schema. |
| Display the CUE schema (or export it for standalone validation). |
| Validate that the cluster meets the deployment prerequisites (read-only; |
| Pull a release from the registry. |
| Generate release configuration (Helm/ArgoCD charts). |
| Deploy a release (Helm or ArgoCD). |
| Uninstall a release. |
| Verify registry authentication by syncing one image and one ORAS artifact. |
| Sync Docker images from the source registry to the target registry: the images that the manifest's enabled features require, or all images with |
| Sync ORAS artifacts from the source registry to the target registry. |
| Report which images that the manifest requires are missing from the target registry, and which images the registry holds that the manifest doesn't require (read-only; exits with a non-zero code if images are missing). |
| Generate Kubernetes secret YAML from schema definitions. |
| Deploy secrets to your Kubernetes cluster. |
| Reconstruct the secrets import file from the secrets already in a cluster. |
| Print a shell completion script (bash, zsh, fish, or PowerShell). |
Global flags
You can use these flags with any command:
- : Path to the manifest in YAML format. The default is
--manifest <path>.auto-discover - : Set the logging level. The options are:
--log-level <level>tracedebug- (default)
info warnerrorfatalpanic
- : Output logs in JSON format.
--json
Logs go to stderr. A command's own output goes to stdout, so a pipeline can capture one without the other. Command output includes a command list, the results, a report, and the commands that a deploy runs.
--dry-runcluster checkverifyExample:
shdctl release pull --version 2.0.0 --log-level debug