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
{{ message }}
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: