-
Notifications
You must be signed in to change notification settings - Fork 25
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
Epic: Hub controller for lighthouse #83
Comments
@donaldh Any specific reason why we need a hub controller and cant make this work without needing a centralized mcscontroller? Having a serverless broker has been one of the core design tenent of submariner. If we want to introduce a central controller to run on broker, it should be with a good enough reason. Note that an mcs controller with come withs own overhead of HA etc. |
Good catch @dfarrell07, I have updated the title and description to match the ER. |
Talked on the planning call - Not a priority for now |
Epic Description
The goal of this epic is to implement ServiceImport merging.
Once an mcs-controller has been introduced, the reconciliation logic will be extended to address
the following open issues:
ServiceExport
objects with theServiceExportConflict
conditionServiceExport
objects into a singleServiceImport
objectRelated enhancement proposal: #111
Acceptance Criteria
Lighthouse behaviour aligns with MCS specification:
Definition of Done (Checklist)
Work Items
The text was updated successfully, but these errors were encountered: