Use multicluster.Aware in provider.Start function signature #23
+2
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is not necessarily something to merge, more of a RFC. I realized we were only using
Engage
in the provider startup, and it seemed to me it would be a nice idea to usemulticluster.Aware
instead of the wholemcmanager.Manager
kitchen sink. This way, you can use the provider in more custom scenarios (in specific, @xrstf and I are currently re-thinking the api-syncagent to move it to multicluster-runtime, and we might not even use themcmanager.Manager
directly).Any thoughts on this?
What Type of PR Is This?
/kind cleanup
/kind api-change
Related Issue(s)
Fixes #
Release Notes