Helm-based PNDA deployment on K8S cluster
<TODO>This is the second part of PNDA Helm Deployment on Rancher based K8s Cluster. In this document, we will see how to configure Kubectl for cluster communication and add persistent volume claims for the required components.
Before configuration of Kubectl for cluster communication, be sure your host machine meets the following prerequisites:
- Installation and a functional state of Rancher Kubernetes cluster.
- Installation of Docker and Kubectl on edge node to communicate Pods, Deployments, Services and PVCs.
- Installation of Helm on edge node for the deployment of PNDA application on Rancher based Kubernetes cluster.
Step-by-step Kubectl Configuration for Cluster Communication
Step 1: Create a .kube directory
Step 2: Get the config file from the Rancher cluster and place it under .kube directory
Helm repository from GIT
Download the PNDA Helm Repo from GIT repository by using the following link,
Configuration of Persistent Volume Claims (PVC) for PNDA
Pods use Persistent Volume Claims (PVC) to request the platform for physical storage. You must create a PersistentVolumeClaim requesting a volume of at least three gibibytes to provide read-write access. Here, we have used NFS-client for storage. For configuring NFS-client storage, you need to modify the values.yaml for the following components,
Step 1: For Redis, HDFS Name Node, HDFS Data Node, Confluent-platform and JupyterHub you have
to modify in /pnda-helm-repo-master/pnda/values.yaml
Step 2: For Package repository, have to modify values.yaml under /pnda-helm-repo-master/pnda/package-repository/values.yaml folder
PNDA Deployment Steps
Please check the following link for PNDA deployment steps,
After successful PNDA deployment, you can see workloads, services and volumes under the namespace which you specify in Rancher UI, as shown below: