CCC 4.5.1 Upgrade Guide
Use the table below to identify your current CCC version and deployment type, and follow the link in the Required Action column to navigate directly to the relevant upgrade procedure.
Before starting any upgrade, create a full backup of the CCC database using the Back up and Restore procedure explained on the Data Management page.
| Current CCC Version | Direct Upgrade to CCC 4.5.1 | Data Preserved | Upgrade Path | Reference |
|---|---|---|---|---|
| CCC 4.0 | No | Yes | 4.0 → 4.2 → 4.3 → 4.5.1 | See CCC 4.0 to 4.5.1 Upgrade Procedure |
| CCC 4.1 | No | Yes | 4.1 → 4.2 → 4.3 → 4.5.1 | See CCC 4.1 to 4.5.1 Upgrade Procedure |
| CCC 4.2 | No | Yes | 4.2 → 4.3 → 4.5.1 | See CCC 4.2 to 4.5.1 Upgrade Procedure |
| CCC 4.3 | Yes | Yes | 4.3 → 4.5.1 | Follow CCC 4.3 to 4.5.1 Upgrade: Podman | Kubernetes | Helm |
| CCC 4.4 | Yes | Yes | 4.4 → 4.5.1 | Follow CCC 4.4 to 4.5.1 Upgrade: Podman | Kubernetes | Helm |
| CCC 4.5 | Yes | Yes | 4.5 → 4.5.1 | Follow CCC 4.5 to 4.5.1 Upgrade: Podman | Kubernetes | Helm |
Upgrade from CCC 4.0 to CCC 4.5.1
This upgrade path applies to environments that are currently running CCC version 4.0. A direct upgrade from CCC 4.0 to CCC 4.5.1 is not supported. To preserve existing data and configuration, you must first upgrade to CCC 4.2, then to CCC 4.3, and then to CCC 4.5.1. To upgrade from CCC 4.0 to CCC 4.5.1:
Back up the existing CCC database using the Back up and Restore procedure explained on the Data Management page.
Upgrade the existing CCC deployment to version 4.2 by following the CCC 4.2 Upgrade Guide.
Verify that the CCC 4.2 service starts successfully and that no startup errors are reported.
After confirming that CCC 4.2 is running correctly, create a new backup of the CCC 4.2 database using the Back up and Restore procedure explained on the Data Management page.
Upgrade from CCC 4.2 to CCC 4.3 by following the CCC 4.3 Upgrade Guide.
Verify that the CCC 4.3 service starts successfully and that no startup errors are reported.
After confirming that CCC 4.3 is running correctly, create a new backup of the CCC 4.3 database using the Back up and Restore procedure explained on the Data Management page.
Proceed with the upgrade from CCC 4.3 to CCC 4.5.1 using the procedure described later in this document.
Upgrade from CCC 4.1 to CCC 4.5.1
This upgrade path applies to environments that are currently running CCC version 4.1. A direct upgrade from CCC 4.1 to CCC 4.5.1 is not supported. To preserve existing data and configuration, you must first upgrade to CCC 4.2, then to CCC 4.3, and then to CCC 4.5.1. To upgrade from CCC 4.1 to CCC 4.5.1:
Back up the existing CCC database using the Back up and Restore procedure explained on the Data Management page.
Upgrade the existing CCC deployment to version 4.2 by following the CCC 4.2 Upgrade Guide.
Verify that the CCC 4.2 service starts successfully and that no startup errors are reported.
After confirming that CCC 4.2 is running correctly, create a new backup of the CCC 4.2 database using the Back up and Restore procedure explained on the Data Management page.
Upgrade from CCC 4.2 to CCC 4.3 by following the CCC 4.3 Upgrade Guide.
Verify that the CCC 4.3 service starts successfully and that no startup errors are reported.
After confirming that CCC 4.3 is running correctly, create a new backup of the CCC 4.3 database using the Back up and Restore procedure explained on the Data Management page.
Proceed with the upgrade from CCC 4.3 to CCC 4.5.1 using the procedure described later in this document.
Upgrade from CCC 4.2 to CCC 4.5.1
This upgrade path applies to environments that are currently running CCC version 4.2. A direct upgrade from CCC 4.2 to CCC 4.5.1 is not supported. To preserve existing data and configuration, you must first upgrade to CCC 4.3, and then to CCC 4.5.1. To upgrade from CCC 4.2 to CCC 4.5.1:
Back up the existing CCC database using the Back up and Restore procedure explained on the Data Management page.
Upgrade the existing CCC deployment to version 4.3 by following the CCC 4.3 Upgrade Guide.
Verify that the CCC 4.3 service starts successfully and that no startup errors are reported.
After confirming that CCC 4.3 is running correctly, create a new backup of the CCC 4.3 database using the Back up and Restore procedure explained on the Data Management page.
Proceed with the upgrade from CCC 4.3 to CCC 4.5.1 using the procedure described later in this document.
Upgrade from CCC 4.3 to CCC 4.5.1
This upgrade path applies to environments that are currently running CCC version 4.3. A direct upgrade from CCC 4.3 to CCC 4.5.1 is supported and allows existing data and configuration to be preserved when the upgrade is performed in the correct sequence. As part of the upgrade process, existing containers, images, and local database directories are removed before CCC 4.5.1 is deployed. For this reason, a full backup of the CCC database must be created before starting the upgrade by following the Back up and Restore procedure explained on the Data Management page.
After the upgrade is complete, cached browser data may cause outdated information to appear in the user interface. Clear your browser cache to ensure that the CCC 4.5.1 interface and features are displayed correctly.
Upgrading from CCC 4.3 to CCC 4.5.1: Podman Users
To upgrade CCC from version 4.3 to 4.5.1 for Podman:
Navigate to the Podman directory and stop the CCC container:
podman-compose down
Verify the removal of the CCC container:
podman ps -a
If a container named ccc appears, remove it:
podman rm -f ccc
Remove the ccc:4.3.0 image from the local repository:
podman rmi -f ccc:4.3.0
Delete the pgdata directory after verifying that a backup has been completed:
sudo rm -rf /home/ccc/pgdata
This step ensures that no residual database state from CCC 4.3 affects the CCC 4.5.1 startup.
Optional: Delete the server-logs directory to remove old logs:
sudo rm -rf /home/ccc/server-logs
Use sudo if required for permissions.
Load the Podman image for CCC 4.5.1 and CCC-DB 4.5.1:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
Provide config in pg_config for CCC-DB 4.5.1.
Add secret in secretfile as required.
Review and update ccc_config for CCC 4.5.1 compatibility:
Review and update secretfile as required:
Optional: Configure the scheduler before starting CCC.
Start the CCC-db container:
sh start-ccc-db.sh
Monitor the CCC-db logs to confirm successful startup:
podman logs -f ccc-db
Start the CCC container:
sh start-ccc-server.sh
Monitor the CCC logs to confirm successful startup:
podman logs -f ccc
Restore your previous data using the Back up and Restore procedure explained on the Data Management page.
Once the upgrade is complete, access CCC using one of the following URLs:
https://host_ip:8181https://hostname:8181
Upgrading from CCC 4.3 to CCC 4.5.1: Kubernetes Users
To upgrade CCC from version 4.3 to 4.5.1 for Kubernetes:
On the master node, remove existing CCC resources:
kubectl delete -f deployment.yaml kubectl delete -f service.yaml kubectl delete -f config-map.yaml kubectl delete -f lunalogs-volume.yaml kubectl delete -f postgres-data.yaml kubectl delete -f packages-volume.yaml kubectl delete -f serverlogs-volume.yaml kubectl delete secrets ccc-password
Remove the ccc:4.3.0 image from all Worker nodes:
crictl rmi ccc:4.3.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Run the following command to determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5.1 image on each Worker node, using the commands for your container runtime:
If your runtime is containerd:
ctr -n=k8s.io images import ccc-db-4.5.1.tar ctr -n=k8s.io images import ccc-4.5.1.tar
If your runtime is CRI-O:
podman load -i ccc-db-4.5.1.tar podman load -i ccc-4.5.1.tar
List images to confirm successful import:
crictl images
Create the CCC secrets for ccc and ccc-db containers on the master node:
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'
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD='password'
Update config-map.yaml for ccc-db.
Start the CCC-DB service:
kubectl apply -f config-map.yaml kubectl apply -f service.yaml kubectl apply -f pv-pvc.yaml kubectl apply -f statefull-deployment.yaml
Monitor CCC-DB logs:
kubectl logs -f <ccc-db-podname>
Update config-map.yaml and deployment.yaml for CCC.
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f <ccc-podname>
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrading from CCC 4.3 to CCC 4.5.1: Helm Users
To upgrade CCC from version 4.3 to 4.5.1 for Helm:
On the master node, uninstall the existing CCC release and remove secrets:
helm uninstall ccc kubectl delete secrets ccc-password
Remove the ccc:4.3.0 image from all Worker nodes:
crictl rmi ccc:4.3.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5.1 image on each Worker node, using the commands for your container runtime:
If your runtime is containerd:
ctr -n=k8s.io images import ccc-db-4.5.1.tar ctr -n=k8s.io images import ccc-4.5.1.tar
If your runtime is CRI-O:
podman load -i ccc-db-4.5.1.tar podman load -i ccc-4.5.1.tar
Verify image availability:
crictl images
Recreate the CCC secrets:
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'
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD='password'
Update values.yaml for CCC and CCC-DB as required.
Start the CCC-DB service:
helm install ccc-db .
Monitor CCC-DB logs:
kubectl logs -f <ccc-db-podname>
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f <ccc-podname>
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrade from CCC 4.4 to CCC 4.5.1
This upgrade path applies to environments that are currently running CCC version 4.4. A direct upgrade from CCC 4.4 to CCC 4.5.1 is supported and allows existing data and configuration to be preserved when the correct procedure is followed. Before starting the upgrade, create a full backup of the CCC database using the Back up and Restore procedure explained on the Data Management page. This backup is required because the upgrade process involves removing existing containers, images, and local data directories before deploying CCC 4.5.1.
After the upgrade is complete, cached browser data may cause outdated information to appear in the user interface. Clear your browser cache to ensure that the latest CCC 4.5.1 interface and features are displayed.
Upgrading from CCC 4.4 to CCC 4.5.1: Podman Users
To upgrade CCC from version 4.4 to 4.5.1 for Podman:
Navigate to the Podman directory and stop the CCC container:
podman-compose down
Verify the removal of the CCC container:
podman ps -a
If a container named ccc appears, remove it:
podman rm -f ccc
Remove the ccc:4.4.0 image from the local repository:
podman rmi -f ccc:4.4.0
Delete the pgdata directory after verifying that a backup has been completed:
sudo rm -rf /home/ccc/pgdata
This step ensures that no residual database state from CCC 4.4 affects the CCC 4.5.1 startup.
Optional: Delete the server-logs directory to remove old logs:
sudo rm -rf /home/ccc/server-logs
Use sudo if required for permissions.
Load the Podman image for CCC 4.5.1 and CCC-DB 4.5.1:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
Provide config in pg_config for CCC-DB 4.5.1.
Add secret in secretfile as required.
Review and update ccc_config for CCC 4.5.1 compatibility:
Review and update secretfile as required:
Optional: Configure the scheduler before starting CCC.
Start the CCC-db container:
sh start-ccc-db.sh
Monitor the CCC-db logs to confirm successful startup:
podman logs -f ccc-db
Start the CCC container:
sh start-ccc-server.sh
Monitor the CCC logs to confirm successful startup:
podman logs -f ccc
Restore your previous data using the Back up and Restore procedure explained on the Data Management page.
Once the upgrade is complete, access CCC using one of the following URLs:
https://host_ip:8181https://hostname:8181
Upgrading from CCC 4.4 to CCC 4.5.1: Kubernetes Users
To upgrade CCC from version 4.4 to 4.5.1 for Kubernetes:
On the master node, remove existing CCC resources:
kubectl delete -f deployment.yaml kubectl delete -f service.yaml kubectl delete -f config-map.yaml kubectl delete -f lunalogs-volume.yaml kubectl delete -f postgres-data.yaml kubectl delete -f packages-volume.yaml kubectl delete -f serverlogs-volume.yaml kubectl delete secrets ccc-password
Remove the ccc:4.4.0 image from all Worker nodes:
crictl rmi ccc:4.4.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Run the following command to determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5.1 image on each Worker node, using the commands for your container runtime:
If your runtime is containerd:
ctr -n=k8s.io images import ccc-4.5.1.tar ctr -n=k8s.io images import ccc-db-4.5.1.tar
If your runtime is CRI-O:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
List images to confirm successful import:
crictl images
Create the CCC secrets on the master node:
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'
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD='password'
Update config-map.yaml and statefull-deployment.yaml for ccc-db as required.
Start ccc-db server:
kubectl apply -f .
Follow logs of database:
kubectl logs -f <postgres-podname>
Update config-map.yaml and deployment.yaml as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f <ccc-podname>
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrading from CCC 4.4 to CCC 4.5.1: Helm Users
To upgrade CCC from version 4.4 to 4.5.1 for Helm:
On the master node, uninstall the existing CCC release and remove secrets:
helm uninstall ccc kubectl delete secrets ccc-password
Remove the ccc:4.4.0 image from all Worker nodes:
crictl rmi ccc:4.4.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5.1 image on each Worker node, using the commands for your container runtime:
If your runtime is containerd:
ctr -n=k8s.io images import ccc-4.5.1.tar ctr -n=k8s.io images import ccc-db-4.5.1.tar
If your runtime is CRI-O:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
Verify image availability:
crictl images
Recreate the CCC secrets:
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'
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD='password'
Update values.yaml as required for ccc-db.
Start ccc-db:
helm install ccc-db .
Follow logs for db:
kubectl logs -f <postgres-pod-name>
Update values.yaml for ccc as required
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f <ccc-podname>
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrade from CCC 4.5 to CCC 4.5.1
This upgrade path applies to environments that are currently running CCC version 4.5. A direct upgrade from CCC 4.5 to CCC 4.5.1 is supported and allows existing data and configuration to be preserved when the correct procedure is followed. Before starting the upgrade, create a full backup of the CCC database using the Back up and Restore procedure explained on the Data Management page. This backup is required because the upgrade process involves removing existing containers, images, and local data directories before deploying CCC 4.5.1.
After the upgrade is complete, cached browser data may cause outdated information to appear in the user interface. Clear your browser cache to ensure that the latest CCC 4.5.1 interface and features are displayed.
Upgrading from CCC 4.5 to CCC 4.5.1: Podman Users
To upgrade CCC from version 4.5 to 4.5.1 for Podman:
Navigate to the Podman directory and stop the CCC container:
podman-compose down
Verify the removal of the CCC container:
podman ps -a
If a container named ccc appears, remove it:
podman rm -f ccc
Remove the ccc:4.5.0 and ccc-db:4.5.0 image from the local repository:
podman rmi -f ccc:4.5.0 podman rmi -f ccc-db:4.5.0
Delete the pgdata directory after verifying that a backup has been completed:
sudo rm -rf /home/ccc/pgdata
This step ensures that no residual database state from CCC 4.5 affects the CCC 4.5.1 startup.
Optional: Delete the server-logs directory to remove old logs:
sudo rm -rf /home/ccc/server-logs
Use sudo if required for permissions.
Load the Podman image for CCC 4.5.1 and CCC-DB 4.5.1:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
Provide config in pg_config for CCC-DB 4.5.1.
Add secret in secretfile as required.
Review and update ccc_config for CCC 4.5.1 compatibility.
Review and update secretfile as required.
Optional: Configure the scheduler before starting CCC.
Start the CCC-db container:
sh start-ccc-db.sh
Monitor the CCC-db logs to confirm successful startup:
podman logs -f ccc-db
Start the CCC container:
sh start-ccc-server.sh
Monitor the CCC logs to confirm successful startup:
podman logs -f ccc
Restore your previous data using the Back up and Restore procedure explained on the Data Management page.
Once the upgrade is complete, access CCC using one of the following URLs:
https://host_ip:8181https://hostname:8181
Upgrading from CCC 4.5 to CCC 4.5.1: Kubernetes Users
To upgrade CCC from version 4.5 to 4.5.1 for Kubernetes:
On the master node, remove existing CCC resources:
kubectl delete -f deployment.yaml kubectl delete -f service.yaml kubectl delete -f config-map.yaml kubectl delete -f lunalogs-volume.yaml kubectl delete -f postgres-data.yaml kubectl delete -f packages-volume.yaml kubectl delete -f serverlogs-volume.yaml kubectl delete secrets ccc-password
Remove the ccc:4.5.0 and ccc-db:4.5.0 image from all Worker nodes:
crictl rmi ccc:4.5.0 crictl rmi ccc-db:4.5.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Run the following command to determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5.1 image on each Worker node, using the commands for your container runtime:
If your runtime is containerd:
ctr -n=k8s.io images import ccc-4.5.1.tar ctr -n=k8s.io images import ccc-db-4.5.1.tar
If your runtime is CRI-O:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
List images to confirm successful import:
crictl images
Create the CCC secrets on the master node:
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'
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD='password'
Update config-map.yaml and statefull-deployment.yaml for ccc-db as required.
Start ccc-db server:
kubectl apply -f .
Follow logs of database:
kubectl logs -f <postgres-podname>
Update config-map.yaml and deployment.yaml as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f <ccc-podname>
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrading from CCC 4.5 to CCC 4.5.1: Helm Users
To upgrade CCC from version 4.5 to 4.5.1 for Helm:
On the master node, uninstall the existing CCC release and remove secrets:
helm uninstall ccc kubectl delete secrets ccc-password
Remove the ccc:4.5.0 and ccc-db:4.5.0 image from all Worker nodes:
crictl rmi ccc:4.5.0 crictl rmi ccc-db:4.5.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5.1 image on each Worker node, using the commands for your container runtime:
If your runtime is containerd:
ctr -n=k8s.io images import ccc-4.5.1.tar ctr -n=k8s.io images import ccc-db-4.5.1.tar
If your runtime is CRI-O:
podman load -i ccc-4.5.1.tar podman load -i ccc-db-4.5.1.tar
Verify image availability:
crictl images
Recreate the CCC secrets:
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'
kubectl create secret generic ccc-db-password --from-literal=DB_PASSWORD='password'
Update values.yaml as required for ccc-db:
Start ccc-db:
helm install ccc-db .
Follow logs for db:
kubectl logs -f <postgres-pod-name>
Update values.yaml for ccc as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f <ccc-podname>
Restore your data using the Back up and Restore procedure explained on the Data Management page.
