Deploying the ECE Composable Services

8 Deploying the ECE Composable Services

You can deploy the Oracle Communications Elastic Charging Engine (ECE) composable services individually or in an existing ECE system.

Topics in this document:

Deploying the ECE Composable Services

Deploying the ECE Composable Services

To deploy the ECE composable services in your cloud native environment:

Create a namespace for the ECE composable services Helm chart:
```
kubectl create namespace EceCompServicesNameSpace
```
where EceCompServicesNameSpace is the namespace in which to create Kubernetes objects for the ECE composable services Helm chart.
Validate the contents of your Helm chart by running the Helm lint command:
```
helm lint --strict oc-ccs-version --values OverrideValuesFile
```
If the command completes successfully, you see output similar to the following:
```
1 chart(s) linted, no failures
```
Validate the values in your override-values.yaml file by using the helm template command:
```
helm template EceCompServicesReleaseName oc-ccs-version
```
where EceCompServicesReleaseName is the release name for oc-ccs-version. Helm uses this name to track the installation instance.

Deploy the ECE composable services by running this command:

helm install EceCompServicesReleaseName oc-ccs-version --namespace EceCompServicesNameSpace --values override-values.yaml

Verify that the pods were deployed successfully by running this command:

kubectl -n EceCompServicesNameSpace get pods

You should see something similar to this:

NAME                                      READY   STATUS     RESTARTS   AGE
cgf-0                                     1/1     Running    0          3d16h
cgf-coordinator-6ff6d9d747-vg2bf          1/1     Running    0          3d16h
nchf-converged-charging-688fd64c6c-zqf8v  1/1     Running    0          3d16h
nchf-nrf-8545d9b5b8-9mz4h                 1/1     Running    0          3d16h