Container ports are exposed after create an ingress to the workload

I’m not sure if this is the desired behavior, but whenever I create an ingress point to the workload, the workload port (specified in the ingress) is exposed to a random port on the host.

In the below figure, the ingress point to the “backend-webapp” workload with port 80

Then, the port 80 of the workload is exposed to port 30075 on the host and I can access the service via that port.

The “backend-webapp” does not contains any port mapping,

1 Like