manage
install-components
Install or upgrade the specified components. The command creates or updates the operators and custom resource objects with the appropriate settings.
- Required role
- Instance administrator You must be an administrator of the projects that are associated with an instance to run this command.
Extended description
Run the install-components to install or upgrade the appropriate
components for your business needs. You can install the components in a batch by specifying a
comma-separated list of components, or you can install components individually.
Syntax
cpd-cli manage install-components \
--license_acceptance=true|false \
--components=<comma-separated-list-of-component-names> \
--release=<version> \
--operator_ns=<project-name> \
--instance_ns=<project-name> \
[--tethered_instance_ns=<comma-separated-list-of-project-names>] \
[--block_storage_class=<RWO-storage-class>] \
[--file_storage_class=<RWX-storage-class>] \
[--storage_vendor=portworx] \
[--image_pull_prefix=<image-location>] \
[--image_pull_secret=<pull-secret-name>] \
[--upgrade=true|false] \
[--skip_components=<comma-separated-list-of-component-names>] \
[--catsrc=true|false] \
[--sub=true|false] \
[--param-file=<file-name>] \
[--run_storage_tests=true|false] \
[--preview=true|false]
Arguments
The install-components command has no arguments.
Options
| Option | Description |
|---|---|
--block_storage_class |
If
the service requires block storage, specify the name of an existing storage class that supports
ReadWriteOnce (RWO) access.
|
--catsrc |
Specify whether to create the catalog source objects for the
specified components. Restriction: This option applies only to
components that use the Operator Lifecycle Manager (OLM) for installation.
If a service uses OLM for installation, you must create the catalog source objects for any services that you plan to install.
|
--components |
A comma-separated list of the components that you want to install or
upgrade.
|
--file_storage_class |
If
the service requires file storage, specify the name of an existing storage class that supports
ReadWriteMany (RWX) access.
|
--image_pull_prefix |
The location from which your cluster pulls
images.
|
--image_pull_secret |
The name of the image pull secret that you created for this instance
of IBM Software Hub.
|
--instance_ns |
The project for the IBM Software Hub control plane and
services.
|
--license_acceptance |
Specify whether you accept the license terms. You must set this
option to true to install the software.
|
--operator_ns |
The project for the IBM Software Hub control plane operators and
service operators.
|
--param-file |
The name of a YAML file that includes additional
parameters. The file must be in the
|
--preview |
Preview the commands that run when you issue this CLI
command. The command issues a series of
The
|
--release |
The release that you want to install or upgrade
to.
|
--run_storage_tests |
Specify whether to validate the performance and functionality of your
storage.
|
--skip_components |
A
comma-separated list of component IDs that are already have cluster-scoped
operators. If you have a cluster-scoped operator for a
component, use this option to prevent the
|
--storage_vendor |
The type of storage that you are using. This setting uses the
recommended storage class when provisioning storage during
installation.
|
--sub |
Specify whether to create the operator subscriptions for the
specified components. Restriction: This option applies only to components
that use the Operator Lifecycle Manager (OLM) for installation.
If a service uses OLM for installation, you must create the operator subscriptions for any services that you plan to install.
|
--tethered_instance_ns |
A
project (namespace) that is tethered to the project where IBM Software Hub is
installed. Important: You must the
setup-tethered-ns command before you run the install-components command with this option.
|
--upgrade |
Specify whether you are upgrading an existing installation. You must
set this option to true to upgrade the software.
|
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.
- Install the specified components
-
cpd-cli manage install-components \ --license_acceptance=true \ --components=${COMPONENTS} \ --release=${VERSION} \ --operator_ns=${PROJECT_CPD_INST_OPERATORS} \ --instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --file_storage_class=${STG_CLASS_FILE} \ --block_storage_class=${STG_CLASS_BLOCK} - Preview the commands to install the specified components on a cluster that uses Portworx storage
-
cpd-cli manage install-components \ --license_acceptance=true \ --components=${COMPONENTS} \ --release=${VERSION} \ --operator_ns=${PROJECT_CPD_INST_OPERATORS} \ --instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --storage_vendor=portworx \ --preview=true