[stable/rabbitmq] GCE error when ingress is set to true

[retpolanne]

Is this a request for help?: Yes

---

BUG REPORT

Version of Helm and Kubernetes:
Helm 2.8.0
Kubernetes 1.9.7

Which chart:
stable/rabbitmq

What happened:
When ingress is set to true on this chart, Helm creates an ingress and sets the rabbit service to ClusterIP. That led to errors like this:

Warning  GCE      5m (x17 over 8m)  loadbalancer-controller   googleapi: Error 400: Invalid value for field 'namedPorts[9].port': '0'. Must be greater than or equal to 1, invalid

What you expected to happen:
According to kubernetes/ingress-nginx#1417 (comment), The service should be of type NodePort and it was created as ClusterIP

How to reproduce it (as minimally and precisely as possible):
Enable the ingress on the helm chart

ingress:
  ## Set to true to enable ingress record generation
  enabled: true

Anything else we need to know:
I'm not sure if you can reproduce the error on AWS.

[jpdasma]

I checked the chart. I think you should also set the following in values.yaml

serviceType: NodePort

[retpolanne]

@jpdasma sorry, I didn't see it. It should work now. Thanks!
(I was also changing the wrong thing, here's the minimal command I used to test:
helm install --dry-run --debug --name test-rabbitmq --set serviceType=NodePort stable/rabbitmq --namespace test-rabbit)