Add FAQ about why we need kube-controller-manager.
Signed-off-by: RainbowMango <qdurenhongcai@gmail.com>
This commit is contained in:
parent
7a1e96ea45
commit
b2f5a0f0fe
|
@ -11,4 +11,12 @@ Both of them are used to hold the propagation declaration, but they have differe
|
||||||
|
|
||||||
## What is the difference between 'Push' and 'Pull' mode of a cluster?
|
## What is the difference between 'Push' and 'Pull' mode of a cluster?
|
||||||
|
|
||||||
Please refer to [Overview of Push and Pull](./userguide/cluster-registration.md#overview-of-cluster-mode).
|
Please refer to [Overview of Push and Pull](./userguide/cluster-registration.md#overview-of-cluster-mode).
|
||||||
|
|
||||||
|
## Why Karmada requires `kube-controller-manager`?
|
||||||
|
|
||||||
|
`kube-controller-manager` is composed of a bunch of controllers, Karmada inherits some controllers from it
|
||||||
|
to keep a consistent user experience and behavior.
|
||||||
|
|
||||||
|
It's worth noting that not all controllers are needed by Karmada, for the recommended controllers please
|
||||||
|
refer to [Recommended Controllers](./userguide/configure-controllers.md#recommended-controllers).
|
||||||
|
|
Loading…
Reference in New Issue