patternkubernetesMinor
components in kubernetes master node?
Viewed 0 times
componentsmasterkubernetesnode
Problem
I'm still a newbie learning the kubernetes and trying to clarify the details.
I've read this document about the components and would like to know the structure of kubernetes master node:
(e.g. deploy "kube-schedulter" on master node A and "kube-controller-manager daemon" on master node B)
I've read this document about the components and would like to know the structure of kubernetes master node:
- is it allowed to deploy the kubernetes control plane components on different master nodes in same cluster?
(e.g. deploy "kube-schedulter" on master node A and "kube-controller-manager daemon" on master node B)
- Is there options to make HA/FT for the master node?
- is it suggested to deploy all the kubernetes control plane components together on a master node no matter what kind of use cases?
- does the deployment of master node(s) support both static IP address and DHCP IP address assignment?
Solution
- I do not see any obstacles. All communication is done through the apiserver over https.
- Multiple replicas of the controller and scheduler are allowed, leader election is built in. All you need is load balancing in front of the apiservers.
- I find this to work best, since usually the failure domain is a node, rather than a component.
- Yes.
Context
StackExchange DevOps Q#11789, answer score: 3
Revisions (0)
No revisions yet.