Manage a local Kubernetes cluster for development
Manage a single local Kubernetes cluster (backed by Kind) for development. The cluster lifecycle is independent of deployah environments. Bring the cluster up, then point a deploy at it with the global --context flag or an environment's "context" field (the cluster's context is "kind-deployah").
deployah cluster [flags]
--context string Kubernetes context to use (overrides the current context and any environment 'context' field)
-C, --cwd string Run as if deployah was started in this directory instead of the current working directory
-d, --debug Enable debug mode (verbose logging and keep temporary files)
-h, --help show help for this command
-k, --kubeconfig string Path to the kubeconfig file to use (defaults to standard kubeconfig resolution)
-n, --namespace string Kubernetes namespace to use for Deployah operations (defaults to current context namespace)
--platform-file string Path to the platform config file (overrides DEPLOYAH_PLATFORM_FILE and the default same-directory lookup)
-s, --spec string Path to the Deployah spec file (YAML or JSON) (default "deployah.yaml")
-t, --timeout duration Timeout for Deployah operations (install/upgrade, list, status, logs, delete, run) (default 10m0s)
- deployah - Deployah turns a spec into a running release on Kubernetes (Spec-to-Release)
- deployah cluster down - Delete the local cluster and stop the cloud provider
- deployah cluster kubeconfig - Print the local cluster kubeconfig path or contents
- deployah cluster status - Show the local cluster status and access info
- deployah cluster up - Create the local cluster and start the cloud provider