[GitHub] [pulsar-helm-chart] wolfstudy closed issue #40: Error: unable to build kubernetes objects from release manifest - Validation Error

wolfstudy closed issue #40: URL: https://github.com/apache/pulsar-helm-chart/issues/40 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

[GitHub] [pulsar-helm-chart] wolfstudy merged pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

wolfstudy merged pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above t

[GitHub] [pulsar-helm-chart] mkozioro commented on issue #39: Bug in podAntiAffinity labels

mkozioro commented on issue #39: URL: https://github.com/apache/pulsar-helm-chart/issues/39#issuecomment-660357711 @rvashishth Could you try with 3 node pool and 5 zookeepers? If affinity works OK, 2 new nodes should be always created. When I was testing couple days ago, I've got 2 zookee

[GitHub] [pulsar-helm-chart] rvashishth commented on issue #39: Bug in podAntiAffinity labels

rvashishth commented on issue #39: URL: https://github.com/apache/pulsar-helm-chart/issues/39#issuecomment-660312628 @mkozioro I tried the anti-affinity on AKS, but I can see pods are scheduled on different AKS nodes as expected. I have tested with 3 node-pool, 3 zookeeper pods. --

[GitHub] [pulsar-helm-chart] NiklasWagner commented on a change in pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

NiklasWagner commented on a change in pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41#discussion_r456465598 ## File path: charts/pulsar/templates/pulsar-manager-deployment.yaml ## @@ -58,7 +58,7 @@ spec: {{ toYaml .Values.pulsar_manager.resources | i

[GitHub] [pulsar-helm-chart] rvashishth commented on a change in pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

rvashishth commented on a change in pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41#discussion_r456455680 ## File path: charts/pulsar/templates/pulsar-manager-deployment.yaml ## @@ -58,7 +58,7 @@ spec: {{ toYaml .Values.pulsar_manager.resources | ind

[GitHub] [pulsar-helm-chart] NiklasWagner commented on pull request #42: Add Ingress to Pulsar Proxy and Pulsar Manager

NiklasWagner commented on pull request #42: URL: https://github.com/apache/pulsar-helm-chart/pull/42#issuecomment-660087223 Ah that what you mean. We're actually using a ingress controller for that which is what most people are doing. We've many ingress resources from many different charts

[GitHub] [pulsar-helm-chart] rvashishth commented on pull request #42: Add Ingress to Pulsar Proxy and Pulsar Manager

rvashishth commented on pull request #42: URL: https://github.com/apache/pulsar-helm-chart/pull/42#issuecomment-660082554 I assume the idea behind ingress to have a single entry point in the k8s cluster. having one ingress-resource per service my not be feasible. I was hoping something as

[GitHub] [pulsar-helm-chart] NiklasWagner commented on pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

NiklasWagner commented on pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41#issuecomment-660076950 Weird that the CI didn't throw an error on your old PR. This should've be definitely catched by the CI. -

[GitHub] [pulsar-helm-chart] NiklasWagner commented on pull request #42: Add Ingress to Pulsar Proxy and Pulsar Manager

NiklasWagner commented on pull request #42: URL: https://github.com/apache/pulsar-helm-chart/pull/42#issuecomment-660075717 I'm not so sure. It would increase the complexity if there is a edge case (for example tls on a different port) and actually there are already 10 *-service.yaml files

[GitHub] [pulsar-helm-chart] rvashishth commented on pull request #42: Add Ingress to Pulsar Proxy and Pulsar Manager

rvashishth commented on pull request #42: URL: https://github.com/apache/pulsar-helm-chart/pull/42#issuecomment-660074223 @NiklasWagner would it be a good idea to create a single ingress resource for all HTTP services( proxy admin API, Grafana, and pulsar-manager) instead of creating multi

[GitHub] [pulsar-helm-chart] rvashishth edited a comment on pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

rvashishth edited a comment on pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41#issuecomment-660071870 Thanks @NiklasWagner This is an automated message from the Apache Git Service. To respond to the

[GitHub] [pulsar-helm-chart] rvashishth commented on pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

rvashishth commented on pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41#issuecomment-660071870 Thanks @NiklasWagne This is an automated message from the Apache Git Service. To respond to the messag

[GitHub] [pulsar-helm-chart] NiklasWagner opened a new pull request #42: Add Ingress to Pulsar Proxy and Pulsar Manager

NiklasWagner opened a new pull request #42: URL: https://github.com/apache/pulsar-helm-chart/pull/42 ### Motivation We're hosting our Pulsar Cluster in kubernetes but most of the actual clients are running on a different infrastructure. To expose the pulsar proxy and the pulsar mana

[GitHub] [pulsar-helm-chart] NiklasWagner opened a new pull request #41: Fix wrong variable reference in Grafana & Pulsar Manager port

NiklasWagner opened a new pull request #41: URL: https://github.com/apache/pulsar-helm-chart/pull/41 Fixes #40 ### Motivation PR #37 updated the location of the ports in the default values yaml. This causes a null pointer exception when rendering this helm chart. #

Jenkins build is back to normal : pulsar-website-build #1071

See

[GitHub] [pulsar-helm-chart] NiklasWagner commented on issue #40: Error: unable to build kubernetes objects from release manifest - Validation Error

NiklasWagner commented on issue #40: URL: https://github.com/apache/pulsar-helm-chart/issues/40#issuecomment-660013099 Same issue. Its a wrong port variable reference in grafana-deployment.yaml and pulsar-manager-deployment.yaml. I'll do a PR on github. --

[GitHub] [pulsar-manager] marcoaureliox opened a new issue #323: JWT_TOKEN - The parameter is not recognized by the docker

marcoaureliox opened a new issue #323: URL: https://github.com/apache/pulsar-manager/issues/323 Hello, I have a pulsar cluster installed, and I'm trying to launch the pulsar-manager through the docker with the simple parameter JWT_TOKEN, but when I have to create an environment on t

Slack digest for #dev - 2020-07-17

2020-07-16 16:03:27 UTC - Chris: I'm working on implementing a form of broker-side filtering of messages and could use a bit of help with pulsar internals. I've got basic filtering via byte pattern and regex working, but am stuck on decoding messages with schema inside the broker. I can get to b