Prerequisites

SCP Software

Following software are required as must to deploy the SCP:

Table 2-1 SCP Software

Software	Version
Kubernetes	v1.12.5
HELM	v2.9.1

Note:

If any of the above services are needed and the respective software is not already installed in the CNE, then install the specified software items before proceeding.

Network access

The Kubernetes cluster hosts must have network access to:

Local docker image repository where the SCP images are available
Local helm repository where the SCP helm charts are available
Service FQDN of SCP must be discoverable from outside of the cluster (i.e., publicly exposed so that ingress messages to SCP can come from outside of Kubernetes).

Note:

All the kubectl and helm related commands used in this guide need to 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

There are some requirements for the laptop/desktop where the deployment commands need to be executed:

It should have network access to the helm repository and docker image repository.
Helm repository must be configured on the client.
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 a namespace in the Kubernetes cluster.
It should have the 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.

SCP Images

Following are the SCP images:

Table 2-2 SCP Images

Microservices	Image
SCP-Worker	scp-worker
SCPC-Pilot	scpc-pilot
SCPC-Soothsayer	soothsayer-configuration
	soothsayer-notification
	soothsayer-subscription
	soothsayer-audit