health runcommand
Run a combination of commands as one command. For example, the cluster, nodes, operands, and operators commands can be started together.
Syntax and command options
The following example shows the syntax that you must use when you run the
runcommand
command:
guardcenter-cli health runcommand \
[--all=true|false] \
[--preinstall]
[--commands=<cluster,network-connectivity,network-performance,nodes,operands,operators,storage-performance,storageclass-validation,security-context,certs,registry,kube-version,airgap>] \
[--control_plane_ns=<instance-controlplane-list>] \
[--include-ns=<instance-namespace-list>] \
[--log-level=debug|trace] \
[--operator_ns=<operator-namespace-list>] \
[--param <path of param.yml file>] \
[--registry-user=<username>] \
[--registry-password=<entitlement-key>] \
[--domain=<domain>] \
[--namespace=<namespace>] \
[--secret=<secret>] \
[--cloud_env={aws|azure|ibm-classic|ibm-vpc}] \
[--host=<local-registry-host>] \
[--username=<local-registry-username>] \
[--password=<local-registry-password>] \
[--version=<guardium-version>] \
[--save] \
[--verbose]
Configure the following command options when you run the
runcommand
command:
Option | Description |
---|---|
--all |
Runs all guardcenter-cli health commands.Tip: The results from
the
storage-performance command are not included in the results of the
--save option. This command produces a separate TAR file when you use the
--all option with runcommand .
Important: Do not use both the
--all and
--commands options at the same time. |
--preinstall |
Runs the guardcenter-cli preinstall validation commands, which include
certs , security-context ,storageclass-validation ,
registry , kube-version , and storage-performance .
|
--commands |
A comma-separated list of commands to run.
Important: Do not use both the
--all and
--commands options at the same time. |
--control_plane_ns |
The Guardium Data Security Center control plane namespace.
|
|
Display command help.
|
--image-prefix |
Specify the image registry prefix.
|
--image-tag |
Specify an image tag for the image that you specified in the --image-prefix option.
|
--include-ns |
Enter a comma-separated list of instance namespaces to gather
guardcenter-cli health information from.
|
--log-level |
The command log level.
|
--operator_ns |
Enter a comma-separated list of operator namespaces.
|
--param |
The path of the param.yml file that includes more parameters for storage
validation and storage performance.
|
|
The minimum amount of bandwidth that is accepted between nodes. The value is in MB per second.
|
--registry-user |
The username that you use to access cp.icr.io.
|
|
The entitlement key that you use to access cp.icr.io.
|
|
The name of the domain that the TLS certificate is issued for.
|
|
The Kubernetes namespace where Guardium Data Security Center is installed.
|
|
The name of the Kubernetes secret that contains the certificates that are to be validated.
|
--cloud_env |
The cloud environment for your cluster. Use this option for more specific information based
on your cloud environment.
|
|
The host of the private registry. This value can be the host IP address or the FQDN and
listening port, which is formatted as <FQDN:Listening_port> .
|
--username |
The username that you use to log in to the private registry.
|
--password |
The password that you use to log in to the private registry.
|
--version
|
The version of Guardium Data Security Center that
you want to use.
|
--save |
Save the output and resource YAML files to the local file system.
|
--verbose |
Display detailed information about resources in table format.
|
Example
The following example runs the
cluster
, nodes
,
operators
, and operands
commands as one
command:guardcenter-cli health runcommand \
--commands=cluster,nodes,operators,operands \
--control_plane_ns=<instance-controlplane-list> \
--operator_ns=<operator-namespace-list> \
--verbose \
--save