Skip to content

Commit c6061bb

Browse files
authored
Merge pull request kubernetes-sigs#9 from multicluster-runtime/sttts-faq
📖 Add small FAQ
2 parents b059da0 + 8ea3fdf commit c6061bb

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,3 +40,16 @@ Run reconcilers that listen to some cluster(s) and operate other clusters.
4040
4. multicluster-runtime is developed as if it was part of controller-runtime (quality standards, naming, style).
4141
5. multicluster-runtime could be a testbed for native controller-runtime functionality, eventually becoming superfluous.
4242
6. multicluster-runtime is provider agnostic, but may contain providers with its own go.mod files and dedicated OWNERS files.
43+
44+
## FAQ
45+
46+
### How is it different from https://github.com/admiraltyio/multicluster-controller ?
47+
48+
In contrast to https://github.com/admiraltyio/multicluster-controller, multicluster-runtime keeps building on controller-runtime for most of its constructs. It is not replacing the manager, the controller or the cluster. To a large degree, this became possible through the extensive use of generics in controller-runtime. Most multicluster-runtime constructs are just type instantiations with a little glue.
49+
50+
### Can I dynamically load provider plugins?
51+
52+
No, plugins are out of scope for now. Multicluster-runtime needs source code changes to
53+
1. enable multi-cluster support by replacing some controller-runtime imports with the multicluster-runtime equivalents and
54+
2. wire supported providers.
55+
The provider interface is simple. So it is not ruled out to have some plugin mechanism in the future.

0 commit comments

Comments
 (0)