-
Notifications
You must be signed in to change notification settings - Fork 36
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
ServiceImport is not recreated if Service is deleted and recreated #693
Comments
From the Export status it looks like GlobalIP is not allocated. @davidohana Can you check the globalingressIPs and check if globalIP is allocated for this service or not? |
@vthapar no globalingressIPs. The recreated service
|
@davidohana Take a look at logs of submariner-globalnet pod if there are any errors in there. IngressIPs should've been allocated for every exported service. |
This is the submariner-globalnet pod output:
|
We don't have a listener that watches for Service, just ServiceExport. I think this is fundamentally the same as submariner-io/submariner#1734. |
This may also be fixed as a part of 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. |
This may be solved as a part of submariner-io/submariner#2130, or more specifically #214. |
Not fixed by this, but triaged for the next release. |
What happened:
If a service is created after ServiceExport already exist, ServiceImport is not created.
What you expected to happen:
ServiceImport shall be created no matter the order of service & service export creation.
How to reproduce it (as minimally and precisely as possible):
monti-host
and backing podsmonti-host
with subctlmonti-host
monti-host
Anything else we need to know?:
Working on a fix for that in the Axon fork.
This is the status of the ServiceExport after step 5 is done:
The text was updated successfully, but these errors were encountered: