Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

accessing branch ingresses #210

Open
mustafakachwala opened this issue Nov 18, 2018 · 0 comments
Open

accessing branch ingresses #210

mustafakachwala opened this issue Nov 18, 2018 · 0 comments

Comments

@mustafakachwala
Copy link

Hi Team,

We are creating a global ingress for our master app deployment and a branch ingress for targetting our branch deployments.
For eg: main app has url https://test.com
branch app has url https://test.com/branchname/build-buildnumber

Now we have two clusters with the above ingresses and have created a multi-ingress using kubemci,

The problem is that when we hit the branch url from the new multi ingress IP, we do not get redirect to the branch ingress.

Question: Will this be supported with kubemci? The problem is that the name of the service.yaml has a dynamic name based on the branch name. Hence, I cannot make it a type:nodeport, as I need to specify the same node port across both clusters, and I will run out of node ports eventually?

Any suggestions as to how I can achieve access to our branch deployment with multi-cluster ingress?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant