GitOps Commands¶
Commands that use the local Hydra context as the source of truth and connect to the Kubernetes API for live operations.
Contents¶
| Command | Description |
|---|---|
| validate-current-context | Verify kubeconfig matches cluster |
| dump | Fetch all live resources |
| list | Print resource IDs from cluster |
| template | Render with cluster context |
| values | Show values including ConfigMaps |
| refs | List transitive references (live) |
| diff | Compare desired vs live state |
| apply | Deploy resources via server-side apply |
| uninstall | Remove Hydra-managed resources |
| status | Check per-app sync status |
| review | Validate refs against live API |
| system | Show preset matches against inventory |
| show | Show central live-resource app assignment |
| untracked | List unmanaged resources |
| inspect | Interactive TUI (live) |
| scale | Scale workloads up/down |
| sync | Control ArgoCD reconciliation |
| backup | Manage backups |
| cert-manager | Certificate management |
Common Usage¶
# Verify connection
hydra gitops validate-current-context prod
# Check what would change
hydra gitops diff 'prod.**'
# Apply changes
hydra gitops apply 'prod.cluster-infra.ingress-nginx'
# Check status
hydra gitops status 'prod.**'
Command Surfaces¶
hydra localworks only with the local Hydra definitions in your workspace.hydra gitopsworks with both the local Hydra definitions and the Kubernetes cluster.hydra clusteris reserved for future cluster-only workflows where the local state is not available.
Cluster Connection¶
All hydra gitops commands require a valid Kubernetes connection. Run hydra gitops validate-current-context <cluster> first to verify.
See Configuration: Kubernetes Context for setup.
For the shared data-preparation flow behind many hydra gitops commands, see Concepts: Cluster Command Data Model.