EKS Cluster Auto Delete Before the Playground Time Ends

I am trying to deploy my practice Lab in AWS EKS Service.

Once I triggered the EKS cluster creation named “IAMTHEONE”. The status soon showed as “Creating” for almost 10 minutes. Hence I chose to leave idle for some time and the playground was having 112 minutes left but when I checked back my EKS cluster was gone.

If this clean up is done intentionally. I am not willing to pay for something not even persist till the end of the Playground Count down.

Let me know how do I claim a refund since creating a free account will provide me more flexibility and persistence which you guys straight deny in monthly subscription.

Kindly revert ASAP, wasted enough time exploring the playground and this kind of events are evident and intentionally being scheduled.

1 Like

Hi @JSM

Thank you for reaching out and for your feedback.

The resources created in the Playground remain until the specified time, and only then are cleaned up.

Can you please share if this happened to you on every attempt or only once?

I am facing the similar issues, it’s autodeleting

aws_eks_cluster.demo_eks: Still creating… [07m51s elapsed]
aws_eks_cluster.demo_eks: Still creating… [08m01s elapsed]

│ Error: waiting for EKS Cluster (demo-eks) create: unexpected state ‘DELETING’, wanted target ‘ACTIVE’. last error: %!s()

│ with aws_eks_cluster.demo_eks,
│ on eks.tf line 25, in resource “aws_eks_cluster” “demo_eks”:
│ 25: resource “aws_eks_cluster” “demo_eks” {

Apply complete! Resources: 27 added, 0 changed, 0 destroyed.

Outputs:

NodeAutoScalingGroup = “eks-cluster-stack-NodeGroup-vht0mCpXZ6JI”
NodeInstanceRole = “arn:aws:iam::644118594096:role/eksWorkerNodeRole”
NodeSecurityGroup = “sg-0c6a9cf1e3b55b067”
random@random:~/amazon-elastic-kubernetes-service-course/eks$ aws eks update-kubeconfig --region us-east-1 --name demo-eks

Cluster status is DELETING


Same here. Starts autodeleteing right after bringing it up. I thought you guys would finally fix so we can use our custom terraform to bring up EKS, but now even with your workaround it’s deleting. Strange…

Generally, we recommend the approach in our tutorial for creation of an EKS cluster; please see our tutorials here. If you’re doing something custom, it would help us to lot to see what code you’re using. Please paste it here using “code blocks”, which look like this when you edit them:

Don’t paste into the editor directly – it will corrupt your code rendering it useless.