With this change, servicePort=0 can be used to disable http port on service for the services exposed by LoadBalancer(for ex: proxy-service) and TLS is terminated at LB.
This is helpful in the below scenario:
SSL/TLS terminated at Load Balancer and therefore LB sends HTTP traffic to service.
We use overrideServiceTargetPort to map service TLS port to container HTTP port.
However, service still keeps exposing HTTP port which is not desired however its required to expose the http port on container.
where its desired to only enable TLS in service however the TLS port in service is mapped to http port in container.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
fixes #
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[x] PR is based off the current tip of the main branch.
[ ] Changes are documented under the "Unreleased" header in CHANGELOG.md
[x] New or modified sections of values.yaml are documented in the README.md
What this PR does / why we need it:
With this change, servicePort=0 can be used to disable http port on service for the services exposed by LoadBalancer(for ex: proxy-service) and TLS is terminated at LB. This is helpful in the below scenario:
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
main
branch.