Skip to main content

Does my app need an ingress?

Is your application public or private?

If your application is public then you’ll need to configure an ingress making sure you’ve considered the security implications associated with this.

If not then you don’t need an ingress, this is also true if your application is being called by another application within the cluster, you can use the internal service address. Your service address is in the format:


You can query your service using kubectl -n $namespace describe service $yourservice.

Applications in development

If your application is in development and contains sensitive information or requires authentication but does not have it set up then adding an ingress may not be a good idea.

Port Forwarding

Instead of opening up your development application to the world you can instead use Kubernetes built in port forwarding. This feature forwards the port defined in your service to your local machine:

kubectl -n $namespace port-forward 8080:8080

This will forward your applications port 8080 to your local machines port 8080. If you visit localhost:8080 in your browser you should see your development application.

A tutorial on using port-forward can be found here.

This page was last reviewed on 18 December 2023. It needs to be reviewed again on 18 June 2024 by the page owner #cloud-platform .
This page was set to be reviewed before 18 June 2024 by the page owner #cloud-platform. This might mean the content is out of date.