Closed chrisbmoore closed 2 years ago
You used to be able to do this with the following in your values.yaml:
service:
type: NodePort
port: 80
targetPort: 8080
portName: http
This configuration used to work for me, however it seems like this configuration was broken some time in the last 60 or so days. Because now the pod refuses connections on any ports when you do a forward.
I'd like to expose Camunda externally to Kubernetes on a set port using a NodePort Service, but I also need a way to specify the
service.ports.nodePort
in my values.yaml. Should there be a PR to add this to the template for NodePort?
I got it working with this https://github.com/camunda-community-hub/camunda-helm/issues/37#issuecomment-1027122551
I'd like to expose Camunda externally to Kubernetes on a set port using a NodePort Service, but I also need a way to specify the
service.ports.nodePort
in my values.yaml. Should there be a PR to add this to the template for NodePort?