New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing charts #152

Closed

HankHannah opened this issue Feb 16, 2022 · 2 comments

HankHannah commented Feb 16, 2022

Using current master branch helmcharts
Download dev-values.yaml
helm install pulsar-hank -n hank-test -f dev-values.yaml ./pulsar/
Out: Error: found in Chart.yaml, but missing in charts/ directory: kube-prometheus-stack, cert-manager, keycloak

Collaborator

eolivelli commented Feb 16, 2022

You should run helm dependency update

Collaborator

eolivelli commented Feb 16, 2022

You can follow the instructions on the README

lhotari closed this as completed

pgier pushed a commit to pgier/datastax-pulsar-helm-chart that referenced this issue


          Fix datastax#152 Add Helm chart support for Istio port naming (attemp…

5b10f48

…t 2) (datastax#162)

Fixes datastax#152 

### Motivation

Support prefix in front of port names to abide by Istio protocol rules
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection

### Modifications

Support adding a prefix
- pulsar -> tcp-pulsar
- pulsarssl --> tls-pulsarssl etc

pgier pushed a commit to pgier/datastax-pulsar-helm-chart that referenced this issue


          Missing fix for datastax#152. Bookie Service also needs the prefix on…

… the port name (datastax#172)

Fixes datastax#158 (This is the second PR - see also apache/pulsar-helm-chart#162)

### Motivation

* All non-standard port-names need a proper protocol prefix to support Istio
 https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
 
### Modifications

Add the prefix value before `bookie`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment