1b680d3a54
This patch allows tls to be enabled with an empty secretName for ingress controllers might be able to provide a default certificate. Fixes #5858, provides better defaults for the Ingress object and allows TLS to be enabled with an empty secretName. ### Motivation The current helm chart can create an Ingress with TLS, but it requires a secretName to be added. This is not an Ingress requirement and, in some cases, the ingress controller can provide a default certificate when the Ingress object does not declare one. ### Modifications Modifications include `values.yaml` and `dashboard-ingress.yaml` to address the issue.
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/