frankjkelly opened a new issue #158: URL: https://github.com/apache/pulsar-helm-chart/issues/158
**Describe the bug** Istio expects port names to abide by a certain convention https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection ``` This can be configured in two ways: By the name of the port: name: <protocol>[-<suffix>]. In Kubernetes 1.18+, by the appProtocol field: appProtocol: <protocol>. The following protocols are supported: http http2 https tcp tls grpc grpc-web mongo mysql* redis* udp (UDP will not be proxied, but the port can be explicitly declared as UDP) ``` **To Reproduce** Pulsar ports are named as `bookie` https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/bookkeeper-service.yaml#L35-L36 `pulsar` https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/broker-service.yaml#L37-L38 `pulsarssl` https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/broker-service.yaml#L43-L44 and several other examples **Expected behavior** Pulsar Helm chart supports Istio port naming standard -- 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 to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
