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

Support clusters in different VPC networks #144

Open
pierrejdsouza opened this issue Mar 7, 2018 · 3 comments
Open

Support clusters in different VPC networks #144

pierrejdsouza opened this issue Mar 7, 2018 · 3 comments

Comments

@pierrejdsouza
Copy link

I created 2 clusters in different regions. And I have a custom URL /healthcheck that will be used for the health check. So what happens is that I can create the ingress on HTTPS with HTTPS healthchecks, but i have to manually change the URL to /healthcheck and I have to add a Host because it is using HTTPS.

The funny thing is that, if you go to the GCLB, 1 of the region is marked as 1/1, meaning it is accepting traffic, while the other is marked as 0/1. I assume that manually changing healthcheck once its created did this probably?

Any ideas?

@pierrejdsouza
Copy link
Author

OK, found the problem, it seems that when creating the ingress, it only created 1 firewall rule. The 2 regions I created have 2 seperate VPCs. So I had to manually create the firewall rule for the 2nd network in order for the health check to work.

@G-Harmon
Copy link
Contributor

G-Harmon commented Mar 8, 2018

@nikhiljindal , is this the potential issue we discussed today where we would not do the right thing if 2 member MCI clusters were in different networks? If so, I think we should keep this open as something to eventually support.

@G-Harmon G-Harmon reopened this Mar 8, 2018
@nikhiljindal nikhiljindal changed the title Issues with healthcheck Support clusters in different VPC networks Jul 10, 2019
@nikhiljindal
Copy link
Contributor

xref #222 which aims to fix this

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

3 participants