Make service ports configurable

[rios0rios0]

It allows the practitioner to change the ports of each service. Now, I'm using the chart and I'm not able to expose the load balancers with the port 80 because of that. With this code, I'm solving this issue.

[rios0rios0]

I made some comments to explain some points.

[nscuro]

Now, I'm using the chart and I'm not able to expose the load balancers with the port 80 because of that.

Can you elaborate on your problem? How are you configuring the load balancing and why do the hardcoded service ports prevent your setup from working?

[rios0rios0]

Now, I'm using the chart and I'm not able to expose the load balancers with the port 80 because of that.

Can you elaborate on your problem? How are you configuring the load balancing and why do the hardcoded service ports prevent your setup from working?

Well, when you try to create 2 load balancers, they will be pointing to an external IP in port 8080. I'm required to type the port. And if I create a DNS like CloudFlare for those external IPs, it won't work in port 80. I'll have to make extra effort to have it working in port 80. Like patching the services, or creating my own services (which is the approach I'm doing). Look at the SonarQube Helm Chart for example: https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube/values.yaml#L68. If they don't do that, I'll be obligated to type: sonar.mycompany.com:9000. Which actually is not so helpful, or seamless.

[nscuro]

Ah I see, so you're using service.type: LoadBalancer then? I think I got a bit confused as to what load balancer you meant. So far most people just use an ingress instead of exposing the services directly.

[rios0rios0]

Ah I see, so you're using service.type: LoadBalancer then? I think I got a bit confused as to what load balancer you meant. So far most people just use an ingress instead of exposing the services directly.

Yes! I'm exposing both directly, and I have DNS for both. Yes! I'm using LoadBalancer.