mayadata-io / mayadata-io/oep-e2e-aws
AWS pipeline resource cleanup [Manual Steps]
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Steps:
- Delete clusters(cluster1, cluster2, c;uster3) created by kops by running kops delete command in CLI.
Ex. kops delete cluster --name k8s-aws-cluster1-11157.k8s.local --state s3://k8s-bucket-aws-cluster1-11157 --yes
Note: cluster name : k8s-aws-cluster1-11157.k8s.local and state: s3://k8s-bucket-aws-cluster1-11157,
Get cluster name and state value from logs for each cluster. - Delete S3 bucket created for every cluster using UI
- Check for EC2 instance for clusters, if exists in running state, then terminate it using UI
- Delete volume attached to the clusters using UI
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files or tests. Start with the listed kops CLI command and the cluster details in the pipeline logs, then follow the AWS UI cleanup steps for S3, EC2, and volumes; done means each listed cluster resource has been removed or confirmed absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, shell
- Domain
- cloud, devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100