Skip to content

Note automatic EFS cleanup during EKS teardown #243

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.

Sign up for GitHub

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

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Note automatic EFS cleanup during EKS teardown #243

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions cloud-accounts/deleting-a-cluster.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ Before deleting your cluster:
- **EC2**: No instances, load balancers, or security groups related to the cluster
- **EKS**: No clusters remaining
- **VPC**: No VPCs created by Porter
- **EFS**: Porter-managed EFS file systems in the cluster VPC are deleted automatically during teardown
- **ECR**: Container images may remain (delete manually if not needed)
</Step>
</Steps>
Expand Down
4 changes: 4 additions & 0 deletions other/deleting-dangling-resources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ First, navigate to the **VPC** section in your AWS console to see the VPC's that

Deleting the EKS cluster and associated auto scaling groups and launch configurations will ensure your EC2 nodes are also terminated; you can navigate to the **Instances** section on the EC2 dashboard to confirm.

### Removing EFS File Systems[](#removing-efs-file-systems "Direct link to heading")

Porter-managed EFS file systems associated with the cluster's VPC are deleted automatically during cluster teardown. If any EFS file systems remain (for example, because cluster deletion was interrupted), navigate to the **EFS** section in your AWS console, locate any file systems tagged with your cluster's VPC ID, and delete them along with their mount targets before removing VPC resources.

### Removing VPC Resources[](#removing-vpc-resources "Direct link to heading")

Navigate to the **VPC** section in your AWS console to see the VPC's that are currently in use. Select the VPC that belongs to the cluster you've provisioned, and copy the VPC ID.
Expand Down