Answers: <ol>
  <li>I do not see any obstacles. All communication is done through the apiserver over https.</li>
  <li>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.</li>
  <li>I find this to work best, since usually the failure domain is a node, rather than a component.</li>
  <li>Yes.</li>
  </ol>
  
Answers: CC BY-SA 4.0
Answers: 2020-07-01T03:46:30.633Z
Answers: excellent answer!!! this is helpful!! please allow me to raise another question:
  5. is it doable to run control plane components and containers on a node together?
Answers: user53815
Answers: CC BY-SA 4.0
Answers: 2020-07-02T08:21:38.977Z
Answers: @user53815 absolutely, and kubeadm, for instance, does just that. It taints the nodes with controlplane components to prevent pods from scheduling there, but nothing is to stop you from running a pod that tolerates these taints. This is something I wouldn't recommend though. In our clusters we run controlplane components as systemd units, rather than static pods, so in our case scheduling there is impossible.
Answers: LLlAMnYP
Answers: CC BY-SA 4.0
Answers: 2020-06-19T19:13:58.857Z
Answers: 2020-06-21T11:31:09.807Z
Answers: 2020-06-21T11:31:09.807Z
Answers: LLlAMnYP
Body: <p>I'm still a newbie learning the kubernetes and trying to clarify the details.</p>
  <p>I've read <a href="https://kubernetes.io/docs/concepts/overview/components/" rel="nofollow noreferrer">this document</a> about the components and would like to know  the structure of kubernetes master node:</p>
  <ol>
  <li>is it allowed to deploy the kubernetes control plane components on different master nodes in same cluster?
  (e.g. deploy &quot;kube-schedulter&quot; on master node A and &quot;kube-controller-manager daemon&quot; on master node B)</li>
  <li>Is there options to make HA/FT for the master node?</li>
  <li>is it suggested to deploy all the kubernetes control plane components together on a master node no matter what kind of use cases?</li>
  <li>does the deployment of master node(s) support both static IP address and DHCP IP address assignment?</li>
  </ol>
  
Tags: <kubernetes>
Title: components in kubernetes master node?
UserDisplayName: user53815
ThreadText: # components in kubernetes master node?
  
  (Asked by: username_0 on 2020-06-09)
  
  I'm still a newbie learning the kubernetes and trying to clarify the details.
  
  I've read [this document](https://kubernetes.io/docs/concepts/overview/components/) about the components and would like to know the structure of kubernetes master node:
  
  1. 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)
  2. Is there options to make HA/FT for the master node?
  3. is it suggested to deploy all the kubernetes control plane components together on a master node no matter what kind of use cases?
  4. does the deployment of master node(s) support both static IP address and DHCP IP address assignment?
  
  **Tags:** kubernetes
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-06-19. Score: 3 | Accepted answer
  
  1. I do not see any obstacles. All communication is done through the apiserver over https.
  2. 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.
  3. I find this to work best, since usually the failure domain is a node, rather than a component.
  4. Yes.
  
  > **Comments:**
  > **username_0**: excellent answer!!! this is helpful!! please allow me to raise another question: 5. is it doable to run control plane components and containers on a node together?  
  > **username_1**: @username_0 absolutely, and kubeadm, for instance, does just that. It taints the nodes with controlplane components to prevent pods from scheduling there, but nothing is to stop you from running a pod that tolerates these taints. This is something I wouldn't recommend though. In our clusters we run controlplane components as systemd units, rather than static pods, so in our case scheduling there is impossible.  
  
  ---
  
  