setting up deployment on multi-node kubernetes
I'm just starting to explore Kubernetes, and there is one thing I find unclear. Suppose I have a master node that I have set up with kubeadm, and another two worker nodes that I had joined to master. Now I have a yaml file that specifies the details of a Deployment and I need to run:
kubectl create -f dep.yaml
Do I need to run this command on master only? and then the master may or may not decide to use both worker nodes for the deployment according to optimal load distribution? Or do I need to run this in all worker nodes?
kubernetes edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
asked Nov 12 '18 at 15:10
Mister_L
523821
add a comment |
I'm just starting to explore Kubernetes, and there is one thing I find unclear. Suppose I have a master node that I have set up with kubeadm, and another two worker nodes that I had joined to master. Now I have a yaml file that specifies the details of a Deployment and I need to run:
kubectl create -f dep.yaml
Do I need to run this command on master only? and then the master may or may not decide to use both worker nodes for the deployment according to optimal load distribution? Or do I need to run this in all worker nodes?
kubernetes edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
asked Nov 12 '18 at 15:10
Mister_L
523821
add a comment |
I'm just starting to explore Kubernetes, and there is one thing I find unclear. Suppose I have a master node that I have set up with kubeadm, and another two worker nodes that I had joined to master. Now I have a yaml file that specifies the details of a Deployment and I need to run:
kubectl create -f dep.yaml
Do I need to run this command on master only? and then the master may or may not decide to use both worker nodes for the deployment according to optimal load distribution? Or do I need to run this in all worker nodes?
kubernetes edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
asked Nov 12 '18 at 15:10
Mister_L
523821
I'm just starting to explore Kubernetes, and there is one thing I find unclear. Suppose I have a master node that I have set up with kubeadm, and another two worker nodes that I had joined to master. Now I have a yaml file that specifies the details of a Deployment and I need to run:
kubectl create -f dep.yaml
Do I need to run this command on master only? and then the master may or may not decide to use both worker nodes for the deployment according to optimal load distribution? Or do I need to run this in all worker nodes?
kubernetes kubernetes edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
asked Nov 12 '18 at 15:10
Mister_L
523821
edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
asked Nov 12 '18 at 15:10
Mister_L
523821
edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
edited Nov 12 '18 at 15:59
Anthon
28.8k1693144
28.8k1693144
asked Nov 12 '18 at 15:10
Mister_L
523821
asked Nov 12 '18 at 15:10
Mister_L
523821
asked Nov 12 '18 at 15:10
Mister_L
523821
523821
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You don't have to. You just need to run this command once and kube-scheduler will schedule it in appropriate node.
Look at the diagram of this page: Concepts Underlying the Cloud Controller Manager
Mster Nodes runs, kube-apiserver, etcd, kube-scheduler, kube-controller-manager and cloud-controller-manager.
kube-scheduler watches for newly created pod and schedule it to appropriate node based on resource requirements, hardware/software/policy constraints, affinity and anti-affinity etc.
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264990%2fsetting-up-deployment-on-multi-node-kubernetes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You don't have to. You just need to run this command once and kube-scheduler will schedule it in appropriate node.
Look at the diagram of this page: Concepts Underlying the Cloud Controller Manager
Mster Nodes runs, kube-apiserver, etcd, kube-scheduler, kube-controller-manager and cloud-controller-manager.
kube-scheduler watches for newly created pod and schedule it to appropriate node based on resource requirements, hardware/software/policy constraints, affinity and anti-affinity etc.
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
add a comment |
You don't have to. You just need to run this command once and kube-scheduler will schedule it in appropriate node.
Look at the diagram of this page: Concepts Underlying the Cloud Controller Manager
Mster Nodes runs, kube-apiserver, etcd, kube-scheduler, kube-controller-manager and cloud-controller-manager.
kube-scheduler watches for newly created pod and schedule it to appropriate node based on resource requirements, hardware/software/policy constraints, affinity and anti-affinity etc.
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
add a comment |
You don't have to. You just need to run this command once and kube-scheduler will schedule it in appropriate node.
Look at the diagram of this page: Concepts Underlying the Cloud Controller Manager
Mster Nodes runs, kube-apiserver, etcd, kube-scheduler, kube-controller-manager and cloud-controller-manager.
kube-scheduler watches for newly created pod and schedule it to appropriate node based on resource requirements, hardware/software/policy constraints, affinity and anti-affinity etc.
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
You don't have to. You just need to run this command once and kube-scheduler will schedule it in appropriate node.
Look at the diagram of this page: Concepts Underlying the Cloud Controller Manager
Mster Nodes runs, kube-apiserver, etcd, kube-scheduler, kube-controller-manager and cloud-controller-manager.
kube-scheduler watches for newly created pod and schedule it to appropriate node based on resource requirements, hardware/software/policy constraints, affinity and anti-affinity etc.
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
edited Nov 12 '18 at 16:07
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
answered Nov 12 '18 at 15:56
Emruz Hossain
1,084210
1,084210
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264990%2fsetting-up-deployment-on-multi-node-kubernetes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
