Installing and deploying Kubernetes Backup Support images
Before you can back up and restore persistent volumes that are attached to your containers, you must install and deploy Kubernetes Backup Support images.
Before you begin
Complete the following tasks:
- Ensure that your system environment meets the requirements that are described in Kubernetes Backup Support requirements and Prerequisites for Kubernetes Backup Support.
- Download the installation file installer-10.1.5.tar.gz from Passport Advantage® Online. For information about downloading files, see technote 1072392.
- Validate the downloaded file by using one of the following methods:
- Verify the MD5 checksum of the downloaded installation file. Ensure that the generated checksum matches the one provided in the MD5 Checksum file, which is part of the software download.
- Verify the signed file that is associated with the installation package by issuing the following
command:
openssl dgst -sha256 -verify IBMSPSignCertificatePublic -signature ./installer-10.1.5.tar.gz.sig ./installer-10.1.5.tar.gz
About this task
During the installation and deployment procedure, you must first update the baas_config.cfg configuration file with specifications for your environment, and then run the installation script baas_install.sh. When you run the installation script, an appropriate Helm Chart is automatically called to deploy Kubernetes Backup Support in your environment.
Procedure
Complete the following steps on the command line in the Kubernetes environment:
Results
Running
state and no components are missing, issue the following
command:kubectl get pods
orkubectl describe pod pod_name
kubectl get pods -n baas
NAME READY STATUS RESTARTS AGE
baas-controller-59dbcf7f94-c6zjr 1/1 Running 0 3h56m
baas-datamover-b44f755c5-k5g2f 1/1 Running 0 22h
baas-etcd-client-59bd5d647f-k76b 1/1 Running 0 2d21h
baas-scheduler-55944fbbb6-b96lw 1/1 Running 0 3h56m
baas-transaction-manager-856b7fd6c94h558 1/1 Running 0 3h32m
baas-etcd-spp-job-control-store-65d9dfb84d-vlqb5 1/1 Running 2 2d17h
If the data mover container is not listed in the output, the data mover container is deployed at run time.
kubectl get services -n baas
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
baas-etcd-client ClusterIP 10.103.44.178 <none> 2379/TCP 2d21h
baas-etcd-spp-job-control-store ClusterIP 10.100.229.67 <none> 2379/TCP 2d21h
baas-scheduler ClusterIP 10.96.33.79 <none> 8000/TCP 2d21h
baas-transaction-manager ClusterIP 10.106.230.11 <none> 5000/TCP 2d21h
The baas-datamover
service is deployed at runtime with type
NodePort
instead of the ClusterIP
range with the TCP protocol.
kubectl get networkpolicies -n baas
NAME POD-SELECTOR AGE
baas-ctl-networkpolicy app=baas,component=controller,release=baas 2d21h
baas-etcd-networkpolicy app=baas,component=etcd-client,release=baas 2d21h
baas-etcd-spp-job-control-store app=baas,component=etcd-spp-job-control-store,release=baas 2d21h
baas-scheduler app=baas,component=scheduler,release=baas 2d21h
baas-transaction-manager app=baas,component=transaction-manager,release=baas 2d21h
The network policy for the data mover is deployed at runtime with the pod-selector
app=baas,component=datamover,release=baas
.
What to do next
After the deployment is completed, ensure that backup operations run correctly by using the
test
service level agreement (SLA) policy to run scheduled backups. For
instructions, see Scheduling backups of persistent volumes.
./baas_install.sh -u