Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / 14391b41d1cea04544e284f502cc4da2eef69d90 / . / kubernetes
tree: 5daff34a4880bdd5779be57b8c93760d4a64766a [path history] [tgz]
  1. aai/
  2. appc/
  3. config/
  4. message-router/
  5. msb/
  6. mso/
  7. oneclick/
  8. policy/
  9. portal/
  10. readiness/
  11. robot/
  12. sdc/
  13. sdnc/
  14. vid/
  15. LICENSE
  16. README.md
  17. README_HELM
kubernetes/README.md

ONAP on Kubernetes

Under construction...

Creating an ONAP deployment instance requires creating base configuration on the host node and then deploying the runtime containers.

The following is an example of creating the first deployed instance in a K8s cluster. The name given to the instance is 'dev1'. This will serve as the Namespace prefix for each deployed ONAP component (ie. dev1-mso).

  1. oom/kubernetes/config/createConfig.sh -n dev1

  2. oom/kubernetes/oneclick/createAll.bash -n dev1

To delete the runtime containers for the deployed instance, use the following:

  1. oom/kubernetes/oneclick/deleteAll.bash -n dev1

Note that deleting the runtime containers does not remove the configuration created in step 1.

To deploy more than one ONAP instance within the same Kubernetes cluster, you will need to specify an Instance number. This is currently required due to the use of NodePort ranges. NodePorts allow external IP:Port access to containers that are running inside a Kubernetes cluster.

Example if this is the 2 instance of an ONAP deployment in the cluster:

  1. oom/kubernetes/config/createConfig.sh -n test

  2. oom/kubernetes/oneclick/createAll.bash -n test -i 2