13dabe6edf
### Motivation
if you deploy pulsar using the helm chart and disable monitoring with
```
extras:
dashboard: no
```
but you have the ingress of the dashboard set to true
```
dashboard:
ingress:
enabled: true
```
the helm chart will create an ingress that points to a non-existing service because the dashboard itself was not deployed.
### Modifications
I've added the same check that is already in place in dashboard-service and dashboard-deployment
### Verifying this change
I dont know of any automated tests, i tested it manually. In the end it's the same "if" that is already in place in dashboard-service and dashboard-deployment
### Does this pull request potentially affect one of the following parts:
Affects deployment via helm chart. An unwanted ingress object is suppressed.
### Documentation
no documentation need
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/