Installing Container Backup Support from IBM Helm Charts Repository and IBM Entitled Registry
You can install Container Backup Support by using the IBM® Helm Charts Repository that is linked to the IBM Entitled Registry.
Before you begin
For the system requirements for Container Backup Support, see Container Backup Support requirements.
- Ensure that you are logged in to the target cluster as a user with
cluster-admin
privileges. - Ensure that internet access is available to pull containers at deployment time.
- Ensure that you complete the installation prerequisites. For instructions, see Installation prerequisites for Container Backup Support.
- Ensure that you set up the installation variables in the baas-options.sh and baas-values.yaml files. For instructions, see Setting up the installation variables.
About this task
You must first prepare your environment by adding the IBM Helm 3 repository to your local repository list and fetching the Container Backup Support Helm package from the IBM Helm Charts Repository. Then, extract the package and use the script that is provided in the Container Backup Support Helm package to deploy Container Backup Support on your Kubernetes or OpenShift cluster.
By using the installation variables that you set up in the baas-options.sh and baas-values.yaml files, the provided script, baas-install-entitled-registry.sh, automatically runs prerequisite tasks and installs Container Backup Support on your cluster. The following tasks are performed automatically:
- Checking for prerequisites.
- Logging in to the IBM Entitled Registry.
- Removing any existing Container Backup Support resources and images.
- Creating the product Kubernetes namespace or OpenShift project (baas) and secret.
- Creating an image pull secret called baas-registry-secret for the namespace (or project) baas. This secret is automatically copied to other namespaces (or projects) of the PVCs that you want to protect.
- Creating custom resource definitions for Container Backup Support and Kafka.
- Pulling the Container Backup Support containers from the IBM Entitled Registry at deployment time.
Procedure
Results
helm3 list -n baas
The output is similar to
the following
example:NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
ibm-spectrum-protect-plus-prod baas 1 2020-10-28 13:15:08.154754539 -0700 MST deployed ibm-spectrum-protect-plus-prod-1.2.0 10.1.8
All of the Container Backup Support pods will load and
change to the Running
state after a few minutes.
Running
state and no components are missing, issue the following
command:kubectl get pods -n baas -w
For Kubernetes, the output is similar to
the following
example:NAME READY STATUS RESTARTS AGE
baas-controller-5f75fc6c9-tmg5l 1/1 Running 0 6h15m
baas-entity-operator-c99f4c49b-p9v9c 3/3 Running 1 6h15m
baas-kafka-0 2/2 Running 0 6h15m
baas-minio-0 1/1 Running 3 6h15m
baas-scheduler-dfdcd9467-88hb5 1/1 Running 0 6h15m
baas-spp-agent-db6b98f85-svdxz 1/1 Running 0 6h15m
baas-strimzi-cluster-operator-7b5c4f9597-88xfn 1/1 Running 0 6h15m
baas-transaction-manager-f654f7f48-7mdxt 3/3 Running 0 6h15m
baas-zookeeper-0 1/1 Running 0 6h15m
baas-zookeeper-1 1/1 Running 0 6h15m
baas-zookeeper-2 1/1 Running 0 6h15m
NAME READY STATUS RESTARTS AGE
amq-streams-cluster-operator-v1.5.3-5b795f4c69-gdsrx 1/1 Running 0 24m
baas-controller-5f75fc6c9-tmg5l 1/1 Running 0 24m
baas-entity-operator-c99f4c49b-p9v9c 3/3 Running 1 24m
baas-kafka-0 2/2 Running 0 24m
baas-minio-0 1/1 Running 3 24m
baas-scheduler-dfdcd9467-88hb5 1/1 Running 0 24m
baas-spp-agent-db6b98f85-svdxz 1/1 Running 0 24m
baas-transaction-manager-f654f7f48-7mdxt 3/3 Running 0 24m
baas-zookeeper-0 1/1 Running 0 24m
baas-zookeeper-1 1/1 Running 0 24mm
baas-zookeeper-2 1/1 Running 0 24m
What to do next
After the deployment is completed, the application host for the Container Backup Support container is automatically registered upon startup of the cluster host in Kubernetes or OpenShift. However, if no clusters are displayed in the page or the page in the IBM Spectrum Protect Plus user interface, automatic registration was unsuccessful. You must then manually register the cluster. For instructions, see Registering a Kubernetes cluster or Registering an OpenShift cluster.