-
Notifications
You must be signed in to change notification settings - Fork 193
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
GlobalNet- exported service isn't reachable after service re creation #1734
Comments
Currently Globlanet controller does not process Service creation/updation events and it only processes delete events. In order to handle this use-case we will have to enhance the code to process create events for Services. |
This might be fixed by submariner-io/enhancements#111. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
@sridhargaddam says there is a work-around for this, lowering prio. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This will also fix submariner-io/lighthouse#693. |
Fixes submariner-io#1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Fixes submariner-io#1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Fixes submariner-io#1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Fixes submariner-io#1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Fixes submariner-io#1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Fixes #1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Fixes submariner-io/submariner#1734 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
What happened:
a. I created a service (default/nginx) on cluster1 and export it
b. I was able to access the service from cluster2.
a. delete the (default/nginx) service from cluster1
b. create a new service with the same name
Though both service and the corresponding serviceexport exist on cluster1, I wasn't able to access default/nginx service from cluster2.
I think that the root cause is that GN controller removed the Global Ingress IP CR on step 2.a and didn't create it after 2.b
[A]
https://submariner.io/getting-started/quickstart/kind/#verify-manually
What you expected to happen:
Remote service should be reachable
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Kind , reswan + GlobalNet
The text was updated successfully, but these errors were encountered: