Upgrading IBM Sterling Control Center Monitor in a Kubernetes Cluster

This section describes how to upgrade IBM® Sterling Control Center Monitor in a Kubernetes cluster.

Download the certified containerized image.
This step is required for multi EP environment. Skip this step for single EP.
Scale down replica:
```
kubectl scale statefulset cc-app --replicas=1
```
After upgradation step 3 completion Scale up replica:
```
kubectl scale statefulset cc-app --replicas=2
```
Invoke the following command to patch the new image to the statefulset:
```
kubectl patch statefulset <statefulset-name> --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"<new Control Center Image>"}]'
```
Example
```
kubectl patch statefulset cc-app --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"111.22.333.444:5000/ibmscc:62_latest"}]'
```
After executing the patch command, image change is automatically detected. It will upgrade all replicas one by one with reverse ordinal number. When a pod is updated, up and running web server, it will terminate the previous pod and upgrade with the new containerized image.

Control Center has been successfully upgraded to its newest version.

Note: Version change is automatically detected based on the current image and from the InstallationInfo.properties file. Configuration values are also automatically detected and considered before Control Center Engine starts. For upgrading the control center image, you must give all configuration in configCC.properties file.