Restarting CCC Containers
If you need to restart the CCC containers, choose one of the following scenarios based on which container you want to restart:
Restart the ccc-db container
Choose one of the following restart scenarios based on your deployment method:
If there is a change in any config, update the corresponding config file before restarting. If there is a change in any password, update the corresponding secret file. Before stopping any database instance, make sure ccc-app containers are not running.
Restart ccc-db using Podman
Stop and remove the ccc-db container:
podman rm -f ccc-db
Start the container by running the start-up script file present in the <package_path>/ccc-db/podman folder of the distribution package:
sh start-ccc-database.sh
Monitor the ccc-db container logs to check that the container started successfully:
podman logs -f ccc-db
Restart ccc-db using Kubernetes
If there is a change in any password, delete and recreate the secret before continuing.
Delete the existing secret:
kubectl delete secret ccc-db-password
Recreate the secret with the updated password:
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD=''
Delete the existing StatefulSet deployment:
kubectl delete -f statefull-deployment.yaml
Recreate the deployment:
kubectl apply -f statefull-deployment.yaml
Restart ccc-db using Helm
If there is a change in any password, delete and recreate the secret before continuing.
Delete the existing secret:
kubectl delete secret ccc-db-password
Recreate the secret with the updated password:
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD=''
Uninstall the Helm release:
helm uninstall ccc-db
Install the Helm release:
helm install ccc-db
Once the primary node has started, scale to more than one instance of the ccc-db StatefulSet if needed:
kubectl scale --replicas=2 statefulset/postgres
Restart the ccc-app container
Choose one of the following restart scenarios based on your deployment method:
If there is a change in any config, update the corresponding config file before restarting. If there is a change in any password, update the corresponding secret file.
Restart ccc-app using Podman
Stop and remove the ccc container:
podman rm -f ccc
Start the container by running the start-up script file present in the <package_path>/ccc-app/podman folder of the distribution package:
sh start-ccc-server.sh
Monitor the ccc container logs to check that the container started successfully:
podman logs -f ccc
Restart ccc-app using Kubernetes
If there is a change in any password, delete and recreate the secret before continuing.
Delete the existing secret:
kubectl delete secret ccc-password
Recreate the secret with the updated password:
kubectl create secret generic ccc-password \ --from-literal=CCC_TRUSTSTORE_PASSWORD='password' \ --from-literal=CCC_KEYSTORE_PASSWORD='password' \ --from-literal=CCC_CREDENTIALSTORE_PASSWORD='password' \ --from-literal=HSM_PASSWORD1='password' \ --from-literal=CRYPTO_OFFICER_PASSWORD='password' \ --from-literal=HSM_PASSWORD2='password' \ --from-literal=CCC_ADMIN_PASSWORD='password' \ --from-literal=CA_CERTIFICATE_PASSWORD='password' \ --from-literal=CCC_DB_PASSWORD='password'
Delete the old instance of ccc, if it is running:
kubectl delete -f deployment.yaml
Start the CCC server by running the start-up script file present in the <package_path>/ccc-app/kubernates folder of the distribution package:
sh start-ccc-server.sh
Once the first node has started, scale to more than one instance of ccc if needed:
kubectl scale --replicas=2 deployment/ccc-deployment
Restart ccc-app using Helm
If there is a change in any password, delete and recreate the secret before continuing.
Delete the existing secret:
kubectl delete secret ccc-password
Recreate the secret with the updated password:
kubectl create secret generic ccc-password \ --from-literal=CCC_TRUSTSTORE_PASSWORD='password' \ --from-literal=CCC_KEYSTORE_PASSWORD='password' \ --from-literal=CCC_CREDENTIALSTORE_PASSWORD='password' \ --from-literal=HSM_PASSWORD1='password' \ --from-literal=CRYPTO_OFFICER_PASSWORD='password' \ --from-literal=HSM_PASSWORD2='password' \ --from-literal=CCC_ADMIN_PASSWORD='password' \ --from-literal=CA_CERTIFICATE_PASSWORD='password' \ --from-literal=CCC_DB_PASSWORD='password'
Delete the old instance of ccc, if it is running:
helm uninstall ccc
Start the CCC server by running the start-up script file present in the <package_path>/ccc-app/helm folder of the distribution package:
sh start-ccc-server.sh
Once the primary node has started, scale to more than one instance of ccc if needed:
kubectl scale --replicas=2 deployment/ccc-deployment
