The Procedure for Scaling Identity Manager Engine replicas is divided into two parts:
This topic describes a basic use case that you can refer for downscaling Identity Manager Engine replicas.
Understand the process carefully before downscaling the Identity Manager engine replicas.
You can scale down one pod at a time.
Assume that we have 3 instances of Identity Manager engine, and their pod names are:
identityengine-0
identityengine-1
identityengine-2
When you downscale to two Identity Manager engine instances, identityengine-2 will go down.
The following actions are required on identityengine-2 before downscaling:
Migrate/recreate drivers running on instance identityengine-2 to another instance.
Delete the server from the tree.
Run the following command to List Persistent Volume Claims (PVC):
kubectl get pvc -n <namespace>
For example:
kubectl get pvc -n idm
Run the following command to delete PVC of identityengine-2:
kubectl delete pvc -n <namespace> <identityengine replica name>
For example:
kubectl delete pvc -n idm identityenginedata-identityengine-2
Set the engine replica count to 2 in the values.yaml file.
Scale down using the following command:
helm upgrade identity-manager helm_charts/identity-manager-1.1.0.tgz --namespace <namespace> -f values.yaml
Perform the following steps to upscale Identity Manager Engine replicas:
Log in to the Azure portal.
Click .
Increase Identity Manager Engine replica count in the values.yaml file.
Scale up using the following command:
helm upgrade identity-manager helm_charts/identity-manager-1.1.0.tgz --namespace <namespace> -f values.yaml