-
Notifications
You must be signed in to change notification settings - Fork 781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS: Document manual steps for ASG/EC2 deletion #851
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
/cc @Jeffwan |
@maniappan Could you provide more details? Do you mean the existing instances? Or worker nodes? Have you deleted worker node group before you remove EKS cluster? |
Sorry for late response. I just come back from vacation. |
I followed the uninstall instructions. There was some exception in the process, so wen ahead and removed the worker nodes and eks clusters. However the worker nodes were constantly spun up even after terminating.. whole sequence of shutdown process may have to be verified.
…--Mani.
________________________________
From: Jiaxin Shan <[email protected]>
Sent: Wednesday, July 10, 2019 5:43:38 AM
To: kubeflow/website
Cc: Maniappan R; Mention
Subject: Re: [kubeflow/website] EC2 instances getting created even after deleting the EKS cluster. (#851)
Sorry for late response. I just come back from vacation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#851?email_source=notifications&email_token=AAK45K6FAP2MHYLX5AIFFPLP6USTFA5CNFSM4H4DBMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZR4TRY#issuecomment-509856199>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAK45K4RHAP2MQFGRCB2Q5DP6USTFANCNFSM4H4DBMOA>.
|
How do you remove the nodes? from EC2? for Cloud Formation?
Sounds like the instances are still controlled by ASG? Have you deleted ASG? |
Deleted ec2, eks clusters and asg. Asg deletion was not happening due some circular dependendency.
…--Mani.
________________________________
From: Jiaxin Shan <[email protected]>
Sent: Wednesday, July 10, 2019 6:07:45 AM
To: kubeflow/website
Cc: Maniappan R; Mention
Subject: Re: [kubeflow/website] EC2 instances getting created even after deleting the EKS cluster. (#851)
removed the worker nodes
How do you remove the nodes? from EC2? for Cloud Formation?
were constantly spun up
Sounds like the instances are still controlled by ASG? Have you deleted ASG?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#851?email_source=notifications&email_token=AAK45K5CPPHQOADANWUPSYDP6UVNTA5CNFSM4H4DBMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZR542Q#issuecomment-509861482>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAK45K6T42LKHTYBTRFJAW3P6UVNTANCNFSM4H4DBMOA>.
|
Eksctl will delete worker node group cloud formation template first and then eks cluster cloud formation. EC2 instances will be delete along with ASG deletion. If you delete ec2 separately, new instance will be created because ASG has to maintain at desired count. |
Thanks, will it be possible to have the manual steps documented?.
…--Mani.
________________________________
From: Jiaxin Shan <[email protected]>
Sent: Thursday, July 11, 2019 11:23:25 PM
To: kubeflow/website
Cc: Maniappan R; Mention
Subject: Re: [kubeflow/website] EC2 instances getting created even after deleting the EKS cluster. (#851)
Deleted ec2, eks clusters and asg. Asg deletion was not happening due some circular dependendency
Eksctl will delete worker node group cloud formation template first and then eks cluster cloud formation. EC2 instances will be delete along with ASG deletion.
If you delete ec2 separately, new instance will be created because ASG has to maintain at desired count.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#851?email_source=notifications&email_token=AAK45K2LYGMLIUEV43CCRYLP65XRLA5CNFSM4H4DBMOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXPKIQ#issuecomment-510588194>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAK45K7VQKKABDNQX6CBBIDP65XRLANCNFSM4H4DBMOA>.
|
I will wrote more docs in 0.6 release. AWS still have some changes in pending for 0.6 |
/area docs |
Kubeflow on AWS: After deleting EKS cluster and removing the EKS cluster in the AWS, the instances are still getting created, how do we stop the same?
The text was updated successfully, but these errors were encountered: