Internal Ingress

Is there a way to make a Kubenetes Ingress only to accept internal requests instead of accepting external and internal requests?

I know I can setup a internal LoadBalancer but I get no benefits of subdomains that I need.

Following the following tutorial I can have a subdomain but my LoadBalancer would accept external requests—-enabling-pod-communication-through-the-load-balancer-(optional)

  1. Ideally I would setup a internal-only ingress, is that possible?
  2. Is there a way to set a domain+subdomain to a Service(type=loadbalancer) without making it available to the public?

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I believe you don’t need an ingress at all for what you’re trying to do. From inside your cluster, you should be able to reference your service by it’s name directly.

So if you have a service called “my-data-api-service”, other apps in your cluster should be able to directly access it at “http://my-data-api-service/api/v1…” for example.

Does that help?