kubernetes nodes status “NotReady” on autoscaling in aws
Can anybody help me in autoscaling. I am trying to autoscale . Pods used to scale up but when pod scale
upto 16 then all nodes get status "Not Ready" and after few min most of the pods get status unkown.
I am trying to autoscale in aws.
I am using kubernetes version 1.10.10
amd kops version 1.10.0
Please help me in this why not get state "not ready"
amazon-web-services
kubernetes nodes autoscaling asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
add a comment |
Can anybody help me in autoscaling. I am trying to autoscale . Pods used to scale up but when pod scale
upto 16 then all nodes get status "Not Ready" and after few min most of the pods get status unkown.
I am trying to autoscale in aws.
I am using kubernetes version 1.10.10
amd kops version 1.10.0
Please help me in this why not get state "not ready"
amazon-web-services
kubernetes nodes autoscaling asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
add a comment |
Can anybody help me in autoscaling. I am trying to autoscale . Pods used to scale up but when pod scale
upto 16 then all nodes get status "Not Ready" and after few min most of the pods get status unkown.
I am trying to autoscale in aws.
I am using kubernetes version 1.10.10
amd kops version 1.10.0
Please help me in this why not get state "not ready"
amazon-web-services
kubernetes nodes autoscaling asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
Can anybody help me in autoscaling. I am trying to autoscale . Pods used to scale up but when pod scale
upto 16 then all nodes get status "Not Ready" and after few min most of the pods get status unkown.
I am trying to autoscale in aws.
I am using kubernetes version 1.10.10
amd kops version 1.10.0
Please help me in this why not get state "not ready"
amazon-web-services
kubernetes nodes autoscaling amazon-web-services
kubernetes nodes autoscaling asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
asked Nov 22 '18 at 19:30
Rishabh GuptaRishabh Gupta
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is happening because your nodes are not equipped in terms of resources(memory or cpu) to handle more pods and current pods has already consumed most of the resources, hence becomes not ready. To handle this situation, either you can increase the resources on your nodes or you create a cluster which auto scale.
If you can check the resources consumed by pod on each node, it will be very clear. Check the following guide to build large cluster in kubernetes.
https://kubernetes.io/docs/setup/cluster-large/
A guide to create auto scalar cluster here
Hope this helps.
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
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%2f53437104%2fkubernetes-nodes-status-notready-on-autoscaling-in-aws%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
This is happening because your nodes are not equipped in terms of resources(memory or cpu) to handle more pods and current pods has already consumed most of the resources, hence becomes not ready. To handle this situation, either you can increase the resources on your nodes or you create a cluster which auto scale.
If you can check the resources consumed by pod on each node, it will be very clear. Check the following guide to build large cluster in kubernetes.
https://kubernetes.io/docs/setup/cluster-large/
A guide to create auto scalar cluster here
Hope this helps.
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
add a comment |
This is happening because your nodes are not equipped in terms of resources(memory or cpu) to handle more pods and current pods has already consumed most of the resources, hence becomes not ready. To handle this situation, either you can increase the resources on your nodes or you create a cluster which auto scale.
If you can check the resources consumed by pod on each node, it will be very clear. Check the following guide to build large cluster in kubernetes.
https://kubernetes.io/docs/setup/cluster-large/
A guide to create auto scalar cluster here
Hope this helps.
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
add a comment |
This is happening because your nodes are not equipped in terms of resources(memory or cpu) to handle more pods and current pods has already consumed most of the resources, hence becomes not ready. To handle this situation, either you can increase the resources on your nodes or you create a cluster which auto scale.
If you can check the resources consumed by pod on each node, it will be very clear. Check the following guide to build large cluster in kubernetes.
https://kubernetes.io/docs/setup/cluster-large/
A guide to create auto scalar cluster here
Hope this helps.
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
This is happening because your nodes are not equipped in terms of resources(memory or cpu) to handle more pods and current pods has already consumed most of the resources, hence becomes not ready. To handle this situation, either you can increase the resources on your nodes or you create a cluster which auto scale.
If you can check the resources consumed by pod on each node, it will be very clear. Check the following guide to build large cluster in kubernetes.
https://kubernetes.io/docs/setup/cluster-large/
A guide to create auto scalar cluster here
Hope this helps.
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
answered Nov 23 '18 at 3:53
Prafull LadhaPrafull Ladha
3,6781523
3,6781523
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
add a comment |
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80"
– Rishabh Gupta
Nov 23 '18 at 6:23
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
Cluster autoscale means the number of nodes in the cluster increase if your load increases on the nodes
– Prafull Ladha
Nov 23 '18 at 6:27
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
actually cluster used to autoscale when I use this "kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m --expose --port=80" And autoscale "kubectl autoscale deployment php-apache --cpu-percent=5 --min=2 --max=20" Then cluster used to autoscale. nodes use to autoscale. And status also show ready. But When I autoscale the microservice base then it after 16 pods node status change to "Node Ready" .
– Rishabh Gupta
Nov 23 '18 at 6:29
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
can anybody help in this?
– Rishabh Gupta
Nov 27 '18 at 18:22
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.
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%2f53437104%2fkubernetes-nodes-status-notready-on-autoscaling-in-aws%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
