Environment Setup

Note:

This section is applicable only when the Policy Control Function (PCF) is deployed in the environment, other than OCCNE.

Network access

The Kubernetes cluster hosts must have network access to:

Local helm repository, where the PCF helm charts are available.
To check if the Kubernetes cluster hosts have network access to the local helm repository, execute the following command:
```
helm repo update
```
Note:
Some of the systems may need to use helm command with admin.conf file as follows:
```
helm --kubeconfig admin.conf
```
Local docker image repository, where the PCF images are available.
To check if the Kubernetes cluster hosts have network access to the local docker image repository, pull any image with tag name to check connectivity by executing the following command:
```
docker pull docker-repo/image-name:image-tag
```
where:
docker-repo is the IP address or host name of the repository.

image-name is the docker image name.

image-tag is the tag the image used for the PCF pod.

Note:

All the kubectl and helm related commands that are used in this guide must be executed on a system depending on the infrastructure/deployment. It could be a client machine, such as, a VM, server, local desktop, and so on.

Client Machine Requirements

Following are the requirements for the client machine where the deployment commands shall be executed:

It should have network access to the helm repository and docker image repository.
It should have network access to the Kubernetes cluster.
It should have necessary environment settings to run the kubectl commands. The environment should have privileges to create namespace in the Kubernetes cluster.
It should have helm client installed with the push plugin. The environment should be configured so that the helm install command deploys the software in the Kubernetes cluster.

Server or Space Requirements

For information on the server or space requirements, see the Oracle Communications Cloud Native Environment (OCCNE) Installation Guide.