How does KOPS recreate the Master Node in AWS?Kops doesn't create aws autoscaling groups for cluster autoscaler addonhow to add an node to my kops cluster? (node in here is my external instance)Connection refused on KOPS deployed master node in kubernetes cluster hosted on AWSHow to start a new node in Kubernetes using kops?Kubernetes: Combining a Kops cluster to an on-premise Kubeadm clusterAccessing Kubernetes master and nodesDisaster Recovery Kops Kubernetes Master Node on AWSChange Kops deployment styleHow to resize K8s cluster with kops, cluster-autoscaler to dynamically increase MastersKops Create Cluster fails with gossip in AWS Linux
!I!n!s!e!r!t! !n!b!e!t!w!e!e!n!
Add dupe check parameter to an API call - Contact Form 7 plugin
Expressing a chain of boolean ORs using ILP involving different variables
Thread-safe, Convenient and Performant Random Number Generator
Changing a TGV booking
The teacher logged me in as administrator for doing a short task, is the whole system now compromised?
Is it safe to remove the bottom chords of a series of garage roof trusses?
Was 'help' pronounced starting with a vowel sound?
Most practical knots for hitching a line to an object while keeping the bitter end as tight as possible, without sag?
Ask for a paid taxi in order to arrive as early as possible for an interview within the city
Something in the TV
Vacuum collapse -- why do strong metals implode but glass doesn't?
How to think about joining a company whose business I do not understand?
How to avoid using System.String with Rfc2898DeriveBytes in C#
Should my "average" PC be able to discern the potential of encountering a gelatinous cube from subtle clues?
Nuclear decay triggers
Did the twin engined Lazair ultralight have a throttle for each engine?
Can we save the word "unique"?
Are there any plans for handling people floating away during an EVA?
jersey vs sweater
How to decide whether an eshop is safe or compromised
Why does my house heat up, even when it's cool outside?
Sous vide chicken without an internal temperature of 165 °F (75 °C)
Metal that glows when near pieces of itself
How does KOPS recreate the Master Node in AWS?
Kops doesn't create aws autoscaling groups for cluster autoscaler addonhow to add an node to my kops cluster? (node in here is my external instance)Connection refused on KOPS deployed master node in kubernetes cluster hosted on AWSHow to start a new node in Kubernetes using kops?Kubernetes: Combining a Kops cluster to an on-premise Kubeadm clusterAccessing Kubernetes master and nodesDisaster Recovery Kops Kubernetes Master Node on AWSChange Kops deployment styleHow to resize K8s cluster with kops, cluster-autoscaler to dynamically increase MastersKops Create Cluster fails with gossip in AWS Linux
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm experimenting Kops on AWS. My cluster is composed by 1 master node and 3 worker nodes. All works fine and in order to test a Master node failure i terminated the corresponding EC2 instance and of course the AutoScaling group handled that problem and created a new instance and it became the the new Master node. So is fine.
My question is how the AutoScaling group did to configure the new EC2 instance to properly be configured as a Master Kubernetes node ? Is there any predefined AMI created when i setup KOPS ? Or is there any user data script that is launched each time a new instance is created ?
Thanks.
amazon-web-services
kubernetes kops asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
add a comment |
I'm experimenting Kops on AWS. My cluster is composed by 1 master node and 3 worker nodes. All works fine and in order to test a Master node failure i terminated the corresponding EC2 instance and of course the AutoScaling group handled that problem and created a new instance and it became the the new Master node. So is fine.
My question is how the AutoScaling group did to configure the new EC2 instance to properly be configured as a Master Kubernetes node ? Is there any predefined AMI created when i setup KOPS ? Or is there any user data script that is launched each time a new instance is created ?
Thanks.
amazon-web-services
kubernetes kops asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
add a comment |
I'm experimenting Kops on AWS. My cluster is composed by 1 master node and 3 worker nodes. All works fine and in order to test a Master node failure i terminated the corresponding EC2 instance and of course the AutoScaling group handled that problem and created a new instance and it became the the new Master node. So is fine.
My question is how the AutoScaling group did to configure the new EC2 instance to properly be configured as a Master Kubernetes node ? Is there any predefined AMI created when i setup KOPS ? Or is there any user data script that is launched each time a new instance is created ?
Thanks.
amazon-web-services
kubernetes kops asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
I'm experimenting Kops on AWS. My cluster is composed by 1 master node and 3 worker nodes. All works fine and in order to test a Master node failure i terminated the corresponding EC2 instance and of course the AutoScaling group handled that problem and created a new instance and it became the the new Master node. So is fine.
My question is how the AutoScaling group did to configure the new EC2 instance to properly be configured as a Master Kubernetes node ? Is there any predefined AMI created when i setup KOPS ? Or is there any user data script that is launched each time a new instance is created ?
Thanks.
amazon-web-services
kubernetes kops amazon-web-services
kubernetes kops asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
asked Mar 27 at 15:28
user1297406user1297406
1061 silver badge11 bronze badges
1061 silver badge11 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is because kops has the concept of instance groups. On AWS they are directly mapped to AutoScalingGroup - which is a similar concept. You can check your instance groups by running kops get ig and also you can edit and descale your master and nodes to 0 and then relaunch them by kops edit ig nodes/nameofthemaster. The second part is kops State Store. Which is a location where the cluster configuration is located. This maps to the most of the Kubernetes configuration, except some of the resources and for example deployments (so internal state) which are stored in etcd.
So in your case when you delete a master node, the AWS will see that the state of your AutoScalingGroup is 0 instead of 1 so it will recreate the EC2 machine.
Description:DescriptionLaunching a new EC2 instance: i-0e06f8fbb78aca2e6
Cause:CauseAt 2019-04-10T12:54:31Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.
After that Kubernetes will take it's configuration from the S3 bucket and the internal state from etcd. Next question would be how does the etcd survive the deletion of the master. You can check it in your Volumes, as etcd has two separate volumes (just as etcd pods one for events and one main) After you delete the master, volumes go into avalivable state and after the new master EC2 instance is spawned this volumes will be mounted to the new master, and you will restore the internal state (not sure, but I think protokube is also somewhere in the picture).
This is also the reason why you can restore your kops cluster from just s3 bucket as there is all the configuration that kops need to run. Except the internal state, which is in etcd for which you would need some separate backup.
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
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%2f55380929%2fhow-does-kops-recreate-the-master-node-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 because kops has the concept of instance groups. On AWS they are directly mapped to AutoScalingGroup - which is a similar concept. You can check your instance groups by running kops get ig and also you can edit and descale your master and nodes to 0 and then relaunch them by kops edit ig nodes/nameofthemaster. The second part is kops State Store. Which is a location where the cluster configuration is located. This maps to the most of the Kubernetes configuration, except some of the resources and for example deployments (so internal state) which are stored in etcd.
So in your case when you delete a master node, the AWS will see that the state of your AutoScalingGroup is 0 instead of 1 so it will recreate the EC2 machine.
Description:DescriptionLaunching a new EC2 instance: i-0e06f8fbb78aca2e6
Cause:CauseAt 2019-04-10T12:54:31Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.
After that Kubernetes will take it's configuration from the S3 bucket and the internal state from etcd. Next question would be how does the etcd survive the deletion of the master. You can check it in your Volumes, as etcd has two separate volumes (just as etcd pods one for events and one main) After you delete the master, volumes go into avalivable state and after the new master EC2 instance is spawned this volumes will be mounted to the new master, and you will restore the internal state (not sure, but I think protokube is also somewhere in the picture).
This is also the reason why you can restore your kops cluster from just s3 bucket as there is all the configuration that kops need to run. Except the internal state, which is in etcd for which you would need some separate backup.
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
add a comment |
This is because kops has the concept of instance groups. On AWS they are directly mapped to AutoScalingGroup - which is a similar concept. You can check your instance groups by running kops get ig and also you can edit and descale your master and nodes to 0 and then relaunch them by kops edit ig nodes/nameofthemaster. The second part is kops State Store. Which is a location where the cluster configuration is located. This maps to the most of the Kubernetes configuration, except some of the resources and for example deployments (so internal state) which are stored in etcd.
So in your case when you delete a master node, the AWS will see that the state of your AutoScalingGroup is 0 instead of 1 so it will recreate the EC2 machine.
Description:DescriptionLaunching a new EC2 instance: i-0e06f8fbb78aca2e6
Cause:CauseAt 2019-04-10T12:54:31Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.
After that Kubernetes will take it's configuration from the S3 bucket and the internal state from etcd. Next question would be how does the etcd survive the deletion of the master. You can check it in your Volumes, as etcd has two separate volumes (just as etcd pods one for events and one main) After you delete the master, volumes go into avalivable state and after the new master EC2 instance is spawned this volumes will be mounted to the new master, and you will restore the internal state (not sure, but I think protokube is also somewhere in the picture).
This is also the reason why you can restore your kops cluster from just s3 bucket as there is all the configuration that kops need to run. Except the internal state, which is in etcd for which you would need some separate backup.
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
add a comment |
This is because kops has the concept of instance groups. On AWS they are directly mapped to AutoScalingGroup - which is a similar concept. You can check your instance groups by running kops get ig and also you can edit and descale your master and nodes to 0 and then relaunch them by kops edit ig nodes/nameofthemaster. The second part is kops State Store. Which is a location where the cluster configuration is located. This maps to the most of the Kubernetes configuration, except some of the resources and for example deployments (so internal state) which are stored in etcd.
So in your case when you delete a master node, the AWS will see that the state of your AutoScalingGroup is 0 instead of 1 so it will recreate the EC2 machine.
Description:DescriptionLaunching a new EC2 instance: i-0e06f8fbb78aca2e6
Cause:CauseAt 2019-04-10T12:54:31Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.
After that Kubernetes will take it's configuration from the S3 bucket and the internal state from etcd. Next question would be how does the etcd survive the deletion of the master. You can check it in your Volumes, as etcd has two separate volumes (just as etcd pods one for events and one main) After you delete the master, volumes go into avalivable state and after the new master EC2 instance is spawned this volumes will be mounted to the new master, and you will restore the internal state (not sure, but I think protokube is also somewhere in the picture).
This is also the reason why you can restore your kops cluster from just s3 bucket as there is all the configuration that kops need to run. Except the internal state, which is in etcd for which you would need some separate backup.
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
This is because kops has the concept of instance groups. On AWS they are directly mapped to AutoScalingGroup - which is a similar concept. You can check your instance groups by running kops get ig and also you can edit and descale your master and nodes to 0 and then relaunch them by kops edit ig nodes/nameofthemaster. The second part is kops State Store. Which is a location where the cluster configuration is located. This maps to the most of the Kubernetes configuration, except some of the resources and for example deployments (so internal state) which are stored in etcd.
So in your case when you delete a master node, the AWS will see that the state of your AutoScalingGroup is 0 instead of 1 so it will recreate the EC2 machine.
Description:DescriptionLaunching a new EC2 instance: i-0e06f8fbb78aca2e6
Cause:CauseAt 2019-04-10T12:54:31Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.
After that Kubernetes will take it's configuration from the S3 bucket and the internal state from etcd. Next question would be how does the etcd survive the deletion of the master. You can check it in your Volumes, as etcd has two separate volumes (just as etcd pods one for events and one main) After you delete the master, volumes go into avalivable state and after the new master EC2 instance is spawned this volumes will be mounted to the new master, and you will restore the internal state (not sure, but I think protokube is also somewhere in the picture).
This is also the reason why you can restore your kops cluster from just s3 bucket as there is all the configuration that kops need to run. Except the internal state, which is in etcd for which you would need some separate backup.
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
answered Apr 10 at 15:50
aureliusaurelius
1,9101 gold badge5 silver badges16 bronze badges
1,9101 gold badge5 silver badges16 bronze badges
add a comment |
add a comment |
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
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%2f55380929%2fhow-does-kops-recreate-the-master-node-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
