Running CDS on Microk8s

Owned by Jakob Krieg
Last updated: Nov 19, 2020 by Miroslav Miklus
4 min read

Instruction how to run CDS on Microk8s.

System Setup:

Make sure to have the correct versions of Kubernetes, kubectl and Helm installed to match the desired ONAP version. Find out required versions for onap e.g. from https://docs.onap.org/projects/onap-oom/en/latest/oom_cloud_setup_guide.html. Guide is tested on a dedicated linux box (Ubuntu 18_04).

Microk8s:

It is yet not clear which version of Microk8s works for which ONAP release. Successfully tested is Microk8s 1.15 for Frankfurt release. E.g. the latest Microk8s version doesn't work for Frankfurt. Run the following command to install a specific version of Microk8s.


Install Microk8s
snap install microk8s --classic --channel=1.15/stable



Following commands will enable all required add-ons for CDS



Enable add-ons of Microk8s
microk8s enable storage microk8s enable dns



Microk8s 1.15 comes with helm v2.14.3, ONAP Frankfurt release requires helm v2.16.6, you can use snap to install required helm version:

Install Microk8s
snap install helm --classic --channel=2.16/stable


The default storage class  is required in the Helm deploy command later on, therefore take note of it with the following command.

Get storage class of Microk8s



ONAP Helm charts

  1. Clone ONAP Helm charts for specific release including submodules

    git clone --branch frankfurt --recurse-submodules "https://gerrit.onap.org/r/oom"


  2. Change to kubernetes dir

    cd oom/kubernetes


  3. Initialize Helm and configure Tiller

    Configure Tiller



  4. Start Helm service and initialize local Helm repository

    make repo

    # This will do same as:

    helm serve &
    helm repo add local http://127.0.0.1:8879

      

  5. Package ONAP Helm charts

    make

Deploy CDS

Run the following Helm command on oom/kubernetes directory do deploy CDS. Note that '--set global.masterPassword=random' is required for Frankfurt and probably newer releases. Storage class needs to be the one from section of Microk8s setup.

Deploy CDS



Result 

As end result you should see CDS pods running. Note that "cds-sdc-listener" POD will never get up with this setup because it's dependent on SDC.



Port forwarding  for external access to CDS-UI

Ports can be forwarded e.g. to access the CDS-UI from another machine. To forward the CDS-UI Port use the following command.

Take care to provide the right pod name and port number.  The port of CDS-UI can be displayed by:

Afterwards the CDS-UI should be accessible externally.