eecc417495
This change introduces the subcommand `status` to the `airshipctl cluster` command. The `status` command will iterate over all defined custom resources in the target path, check their status against the resources currently in the cluster, and then report results on stdout. Change-Id: Ieaff6b91fd9055f995c5ba8ce79959356a2a8a02 Relates-To: #73
1.2 KiB
1.2 KiB
airshipctl phase render
Render phase documents from model
Synopsis
Render phase documents from model
airshipctl phase render PHASE_NAME [flags]
Examples
# Get all 'initinfra' phase documents containing labels "app=helm" and
# "service=tiller"
airshipctl phase render initinfra -l app=helm,service=tiller
# Get all documents containing labels "app=helm" and "service=tiller"
# and kind 'Deployment'
airshipctl phase render initinfra -l app=helm,service=tiller -k Deployment
Options
-a, --annotation string filter documents by Annotations
-g, --apiversion string filter documents by API version
-h, --help help for render
-k, --kind string filter documents by Kinds
-l, --label string filter documents by Labels
Options inherited from parent commands
--airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config")
--debug enable verbose output
--kubeconfig string Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig")
SEE ALSO
- airshipctl phase - Manage phases