Oracle® Communications Security Edge Proxy Protection (SEPP) Cloud Native Installation Guide Release 1.1 F17667-01 |
|
![]() Previous |
![]() Next |
This procedure describes the steps to deploy SEPP Client on CNE.
Table 3-3 SEPP Client Deployment
Step # | Procedure | Description |
1 ![]() |
Node2: Search helm chart | Execute the following command to check the
version of the helm chart installation.
E.g:
|
2 ![]() |
Node2: Prepare custom_values.yaml file |
Prepare a custom_values.yaml file with the required parameter information. Refer to Client Yaml File and Envoy Yaml File for sample YAML files. |
3 ![]() |
Node2: Navigate to directory where ocsepp-1.0.0.tgz is extracted on Master node | Navigate to directory where ocsepp-1.0.0.tgz is extracted on Master node : |
4 ![]() |
Node2: Deploy Envoy | Execute the following command:
Where: deployment_name and namespace_name: depends on customer configuration customized_yaml_file.yaml: Yaml file after modifying the envoy parameter values based on the requirement. |
5 ![]() |
Node2: Deploy SEPP Client | Execute the following command:
Where: deployment_name and namespace_name: depends on customer configuration customized_yaml_file.yaml: Yaml file after modifying the client parameter values based on the requirement. Note: "SEPP Server Deployment" and "SEPP Client Deployment" should be deployed on SEPP2 and SEPP1 respectively as well to have both mode working on both SEPP nodes. |
6 ![]() |
Node2: Check repo status | Execute
helm
ls to check the deployment status.
|
7 ![]() |
Node2: Check svc status | Check if all the services are deployed and
running:
Note: Status must be Running and Ready must be 1/1. |
8 ![]() |
Node2: Verify SEPP client deployment | Execute command
helm
status <deployment_name> and verify deployment, pod and service
status should be up.
|