-
Notifications
You must be signed in to change notification settings - Fork 1.5k
KEP 1645: add ServiceImport conditions #5439
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MrFreezeex The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I would bring this in the next sig meeting but if you have any comment and/or want to review this prior to the meeting feel free! |
7def6e0
to
e68fa5b
Compare
e68fa5b
to
1c3b48e
Compare
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Arthur Outhenin-Chalandre <[email protected]>
1c3b48e
to
4b5054a
Compare
Agreed this makes sense as a general-purpose mechanism for surfacing issues which can not be discovered at export time. /lgtm |
So far we had the conditions fields only on ServiceExport, trying to implement dual stack on Cilium and Submariner highlighted that there could be some "import time" errors as well. For instance, having an IPv6 only service and trying to import in IPv4 only clusters which in both Cilium and Submariner raise some issue that we would want to report to users via the ServiceImport conditions.
This is not specifically tied to IP protocol/families issues but supposed to be a general thing for implementations to report any errors and status occurring during import time.