The paragraph assumes that Kubernetes has already been installed and kubectl can access the pod.
CORD uses helm to deploy containers on Kubernetes. As such helm should be installed before trying to deploy any CORD container.
Helm documentation can be found at https://docs.helm.sh/
{% include "/partials/helm/description.md" %}
Helm is made of two components:
Helm can be installed on any device able to reach the Kubernetes POD (i.e. the developer laptop, another server in the network). Tiller should be installed on the Kubernetes pod itself, through the kubectl CLI.
Follow the instructions at https://docs.helm.sh/using_helm/#installing-helm
To install tiller type the following commands from any device already able to access the Kubernetes pod.
helm init kubectl create serviceaccount --namespace kube-system tiller kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}' helm init --service-account tiller --upgrade
Once helm and tiller are installed you should be able to run the command helm ls without errors.
Helm charts are the packaging format used by helm. A chart is a collection of files that describe a related set of Kubernetes resources.
CORD uses charts to define each component. For example:
More info on Helm charts at https://docs.helm.sh/developing_charts/#charts