IBM® Sterling Control Center Monitor Clustering using Scaling of deployment
For scaling the Control Center, there are two ways, either you can give replicas value as the number you want to deploy before running stateful file or you can use scale command after deploying one pod successfully. For both approaches you have to ensure following prerequisites:
- If you are using volume claim template as described in Deployment using volumeClaim, create a new
persistent volume and change the name as defined in the
namefield in the volume yaml file used to create the storage. For more information see sample volume yaml file, Creating Persistent Volume in a Kubernetes cluster using NFS.
Create a pod directory hierarchy based on number of pods you'd like to create. For example, to scale your application to up to 3 replicas of a statefulset, cc-app, currently running cc-app-0 pod create the following pod hierarchy:
- Place all required files in
user_inputsdirectory. For more information see, Populating the Volume with required user inputs file.When you will deploy statefulset file with multiple replicas, it will automatically create the number of replicas as you have given in statefulset file. If you have already done deployment using replica as one successfully, you can see the pod details using command:
You can now view the status of pods running inside cluster in the following format:
$ kubectl get pods -o wide
READY STATUS RESTARTS AGE IP NODE NOMINATEDNODE READINESS GATES cc-app-0 1/1 Running 0 19d 10.36.0.3 ccrdock-02 <none> <none>Now you can scale your application using stateful set name such as,
$ kubectl scale statefulset cc-app --replicas=2
This command creates a replica of the existing deployment. Replicas value 2 means there should be two instances in total including the existing deployment.
Note: Here engine name is taken from
configCC.propertiesfile, so in case of scaling you must give different engine name for each pod.