-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
need guidance on multiple namespace and url pattern #1137
Comments
Hi, under current implementation, the ingress must be the same namespace as the service(also the pod). Also, the |
Is there any plan on the roadmap for alb-ingress-controller to support multi-namespace services in the future? This could truly give the advantage of using a single ALB instead of multiple CLBs. At the moment it would force having 1 ALB for each namespace, which is equivalent to our current architecture where there is 1 CLB per environment (because each environment matches a namespace in our EKS cluster) |
+1 |
Is there any update for this can we get support for multiple name spaces. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@julianguinard @nsisodiya closing this issue |
I am doing PoC and here I got stuck.
I have one cluster. in this cluster, there are multiple namespaces.
say
ns1, ns2, ns3
each namespace holds multiple pods, say
p1, p2, p3
etc pod contains only 1 docker container. Their docker containers are basically services. So there are multiple products and each product contains multiple micro-services services.I want to get final urls like
Or url can also be like
I am confused at few things.
Here is the code for creating ingress
this give things like
it is showing that "ingress" is in the namespace but the pod is in the default namespace.
is this a mistake?
Do I need to copy-paste the above code and create another ingress service in a different namespace or just add more rules in the above code?
The text was updated successfully, but these errors were encountered: