feat(helm): configure service port independent of container port #2957
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
I would like to use port 80 as the service port but keep the default container port (or use any other unprivileged port as container port) because I am not very good at remembering (seemingly) random port numbers. It is much easier to remember the address of the Trivy server as http://trivy.trivy.svc than remembering http://trivy.trivy.svc:4954. I do not want to use the privileged port 80 as container port though (and even if I wanted, the container would fail to start with the following error:
FATAL listen tcp 0.0.0.0:80: bind: permission denied
).With the current Helm chart I can only configure the
.service.port
value and this will be used for service's port, the service's targetPort and for the container's port:The text was updated successfully, but these errors were encountered: