You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have already searched this project's issues to determine if a similar question has already been asked.
What is your question?
I have an api that is exposed publicly through nginx ingress. Along that I have an internal endpoint meant to be consumed by services running inside the cluster. How can I only let requests coming from inside the cluster to pass for those endpoints? Are there env variables that are passed to the pods running in the cluster that I can use as such mechanism of IP block.
What primary components of the stack does this relate to?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Prior Search
What is your question?
I have an api that is exposed publicly through nginx ingress. Along that I have an internal endpoint meant to be consumed by services running inside the cluster. How can I only let requests coming from inside the cluster to pass for those endpoints? Are there env variables that are passed to the pods running in the cluster that I can use as such mechanism of IP block.
What primary components of the stack does this relate to?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: