Deployment of CNC Console

This procedure describes the steps to deploy CNCC. The below steps need to be executed from a server which has access to Kubectl and helm commands.

Table 4-2 CNCC Deployment

Step No. Procedure Description

Search helm chart

Execute the following command to search helm chart.

helm search <deployment_name>

Prepare

custom_
					 cncconsole_values.yaml

file

Prepare a

custom_
					 cncconsole _values.yaml

file with the required parameter information.

Note:

The user needs to update the "domain" in the custom_ cncconsole _values.yaml file per the name of cluster (default value of domain is "svc.cluster.local"). If the cluster name is XYZ then domain must be svc.XYZ.
The user needs to update the "clusterDomain" in thecustom_ cncconsole _values.yaml file per the name of cluster (default value of domain is "cluster.local"). If the cluster name is XYZ then domain must be XYZ.

Deploy CNCConsole

Installation using helm repository

Execute the following command:

helm install <helm-repo> -f custom-cncconsole_values.yaml -- name <deployment_name>
 --namespace <namespace_name> --version <helm_version>

Where:

helm-repo: repository name where the helm images, charts are stored

values: helm configuration file which needs to be updated based on the docker registry

deployment_name and namespace_name: depends on customer configuration

For example:

helm
					 install ocscp-helm-repo/ocscp -f custom-cncconsole_values.yaml --name
					 cncconsole --namespace cncc --version1.0.0

Installation using helm tar

Execute the following command:

helm install -f custom-cncconsole_values.yaml --name cncconsole -- namespace
 <namespace> <chartpath>./<chart>.tgz

Check repository status

Execute following command to check the deployment status.

helm status <deployment_name>

Check service status

Check if all the services are deployed and running:

kubectl -n <namespace_name> get services

Sample Output:

cncc-cmservice	NodePort	10.111.117.252	<none>	8442:32585/TCP	2d21h
cncc-ingress	LoadBalancer	10.98.168.84	<pending>	80:30075/TCP	2d21h

Check pod status

Check if all the pods are up and running:

kubectl -n <namespace_name> get pods 
sample output: 
NAME                           READY     STATUS RESTARTS   AGE
cncc-cmservice-6f8c8d889-qskvk 1/1     Running   0          2d21h
cncc-ingress-559844f754-g788s  1/1     Running   0          2d21h