-
Notifications
You must be signed in to change notification settings - Fork 859
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
[MCS] Remove "derived-" prefix of MCS #2384
Comments
Consider providing feature switches. |
+1 But the current issue seems to be pointing to something else. |
Following a discussion in Karmad'a community Slack channel I've tested the following flows to support the service import idea:
Scenario 1
Scenario 2
The way that I implemented this flow is what can be referred to as local-and-remote service discovery. The options could be:
My tested code is missing a lot of the conflict resolution logic and I just created it as a highly tailored PoC. This implementation aligns with the KEP-1645 guidelines and adapts concepts from liqo and submariner for service import. |
Hi @bivas, I'm very sorry for not keeping track of the progress and responding to your reply for such a long time. Recently, I have been busy with other things which caused a delay in this matter. I think your testing and practice are great. Remove the "derived-" prefix from the service, which will be a very user-friendly action and bring us many benefits. Can we further advance this plan? Would you like to propose a proposal so that we can further promote the implementation of this plan in the Karmada community? Apologies again for my delayed response. |
What would you like to be added:
Remove "derived-" prefix of MCS, so user can use the same k8s service name in other k8s clusters.
Why is this needed:
Karmada is supposed to offer one-cluster view. However user need to change there application settings when using MCS.
Maybe there could be an validation to refuse the ServiceImport object when there has been a same-name service in the target cluster.
The text was updated successfully, but these errors were encountered: