manage
get-cr-status
Extended description
- Installed at the correct version
- In maintenance mode during an offline backup
- Shut down to prevent the service from using resources
For each component, the output of the command includes the following information:
- The custom resource kind and name
- The timestamp when the custom resource was created
- The project where the custom resource exists
- The status of the custom resource
- The current progress, as a percent
- The message associated with the current progress
- The version of the component from the
specsection of the custom resource - The version in the
statussection after the last operator reconcile loop - The operator version and build number, if available
The output has the following format:
Components CR Kind CR Name Creation Timestamp Namespace Expected Version Reconciled Version Operator Information Progress Progress Message Reconcile History Status
---------- ------- ------- ------------------ --------- ---------------- ------------------ -------------------- -------- ---------------- ----------------- --------
<ID> <kind> <name> <timestamp> <project> <version> <version> <version> <build> <%> <message> <details> <status>
The following table provides more information about the statuses for each custom resource:
For more information about the statuses that are returned for each component, see Getting the status of installed components.
Syntax
cpd-cli manage get-cr-status \
[--cpd_instance_ns=<project-name>] \
[--tethered_instance_ns=<comma-separated-list-of-project-names>] \
[--cluster_component_ns=<project-name>] \
[--components=<comma-separated-list-of-component-names>] \
[--include_dependency=true|false]
Arguments
The get-cr-status command has no arguments.
Options
| Option | Description |
|---|---|
--components |
A comma-separated list of the components for which you want to see
the status.
|
--cpd_instance_ns |
The project for the IBM Software Hub control plane and
services. If you specify a component that isn't in the project, the output will not include information about the component.
|
--cluster_component_ns |
The project where the cluster-wide component that you want to get the
status of is installed.
|
--filter |
Specify the list of fields to include in the
response.
|
--include_dependency |
Specify whether you want to get the status of the dependencies for
the specified components.
|
--tethered_instance_ns |
The tethered projects where you want to get the status of installed
components.
|
Examples
It is strongly recommended that you use a script to create environment variables with the correct values for your environment. For details, see Setting up installation environment variables.
- Get the status of all components in the specified project
-
cpd-cli manage get-cr-status \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} - Get the status of the control plane in the specified project
-
cpd-cli manage get-cr-status \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --components=zen - Get the status of all components in the specified tethered project
-
cpd-cli manage get-cr-status \ --tethered_instance_ns=${PROJECT_CPD_INSTANCE_TETHERED} - Get the status of all components in the projects associated with the instance
-
cpd-cli manage get-cr-status \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --tethered_instance_ns=${PROJECT_CPD_INSTANCE_TETHERED_LIST} - Get the status of the scheduling service
-
cpd-cli manage get-cr-status \ --cluster_component_ns=${PROJECT_SCHEDULING_SERVICE} \ --components=scheduler