a6d1f86974
### Motivation Fixes feature enhancement request #6143: Currently, there are quite a few undocumented steps that are needed to be performed manually in order to make sure that the functions can be submitted as pods in K8s runtime environment. It would be much better if this process would be automated. #### Proposed solution: Automate this process via helm install and update the helm charts with templates. ### Modifications I've added an additional `functionsAsPods` filed in extra components inside the values file. If the setting is set to `yes`, then it would add `serviceAccount` to the broker deployment. It will also add the rbac policy to give the brokers permissions to deploy functions. The policies can be found in the new `broker-rbac.yaml` template file. Moreover, it will also change the `functions_worker` settings and set the function runtime factory setting that can be found inside `broker-configmap.yaml`. ### Verifying this change 1) Set `functionsAsPods: yes` inside helm values yaml file. 2) Follow the instructions on how deploying helm and run: `helm install pulsar --values pulsar/values-mini.yaml ./pulsar/`. 3) Wait until all the services are up and running. 4) Set up tenant, namespace. 5) Create a function, sink and source and submit it using the CLI to make sure the pods are running alongside the Pulsar cluster. In addition, set up such a flow where the data is flowing from source to topics, the processed by a function and sink outputs the data 6) Push data into cluster through the source and make sure it comes out of the sink into destination. There shouldn't be any errors in the logs of brokers, bookie, sources, sinks and functions. #### Modules affected: The changes in the PR are affecting the deployment using the helm charts. Now the if the flag `functionsAsPods` is set to `yes` inside the `values.yaml. file, the functions would run as pods. ### Documentation Currently, the documentations explaining the helm chart deployment process is lacking and this should be updated.
This directory contains the Helm Chart required to do a complete Pulsar deployment on Kubernetes.
Install Helm
Before you start, you need to install helm. Following helm documentation to install it.
Deploy Pulsar
Minikube
Install Minikube
Install and configure minikube with
a VM driver, e.g. kvm2 on Linux
or hyperkit or VirtualBox on macOS.
Create a K8S cluster on Minikube
minikube start --memory=8192 --cpus=4
Set kubectl to use Minikube.
kubectl config use-context minikube
After you created a K8S cluster on Minikube, you can access its dashboard via following command:
minikube dashboard
The command will automatically trigger open a webpage in your browser.
Install Pulsar Chart
Assume you already cloned pulsar repo in PULSAR_HOME directory.
- Go to Pulsar helm chart directory
cd ${PULSAR_HOME}/deployment/kubernetes/helm - Install helm chart.
helm install --values pulsar/values-mini.yaml ./pulsar
Once the helm chart is completed on installation, you can access the cluster via:
- Web service url:
http://$(minikube ip):30001/ - Pulsar service url:
pulsar://$(minikube ip):30002/