pulsar-helm-chart

Go to file

roman-popenov 4d00b385ac [deployment][helm] Add Grafana ingress template (#6280 )

### Motivation
Exposing Grafana via soft ingress controller so that it can be exposed through a Load Balancer.

#### Proposed solution:
Create ingress template for Grafana so that it can be automatically picked up if ingress controller instance is running in the cluster. The other solutions are to expose Grafana as NodePort or setting it as a LoadBalancer.

### Modifications
Added `grafana-ingress.yaml` template in the templates and an `ingress` section for Grafana in the values file.

### Verifying this change
1) Set ingress to `true` for Grafana in values file and provide hostname. Currently tested with NGINX, but can use another ingress controller, but will need to change the ingress controller class to another one in the template.

2) Add NGINX Helm repository :

```bash
helm repo add nginx-stable https://helm.nginx.com/stable
helm repo update
```
3) Install with Helm 3:

```bash
helm install nginix-ingress-crl nginx-stable/nginx-ingress
```

4) Follow the instructions on how deploying helm and run:
`helm install pulsar --values pulsar/values-mini.yaml ./pulsar/`.

5) Wait until all the services are up and running.

6) Verify that Grafana is accessible via url.

**Path settings**

Currently, by default the path setting is set to `/grafana`. For that to work, the NGINX configuration file `nginx.conf` should have `grafana` sub path enabled:
```
See https://grafana.com/docs/grafana/latest/installation/behind_proxy/

To avoid having to mess with NGINX configurations files `path` can be changed to `/`, but this path might conflict with other services that are being proxied in the cluster.

#### 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
This PR will be adding ingress capability for Grafana and this should be documented.

2020-02-10 00:09:56 -08:00

pulsar

[deployment][helm] Add Grafana ingress template (#6280 )

2020-02-10 00:09:56 -08:00

README.md

[Issue:5787] Fix docs for creating a K8S cluster on Minikube fail (#5805 )

2019-12-06 16:19:37 +08:00

README.md

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/