[Bug]: unable to prepare environment OR delete-environment - Times out waiting for deployment - Deployment not ready.

[Supreeth095]

NOTE: This issue looks super Similar to "https://github.com/aws-samples/eks-workshop-v2/issues/1062"

Installation method

Own AWS account

What happened?

ec2-user:~/environment:$ delete-environment Refreshing copy of workshop repository from GitHub...

Resetting the environment... Tip: Read the rest of the lab introduction while you wait! Waiting for application to become ready... timed out waiting for the condition on deployments/assets timed out waiting for the condition on deployments/carts timed out waiting for the condition on deployments/carts-dynamodb timed out waiting for the condition on deployments/catalog timed out waiting for the condition on deployments/checkout timed out waiting for the condition on deployments/checkout-redis timed out waiting for the condition on deployments/orders timed out waiting for the condition on deployments/orders-mysql timed out waiting for the condition on deployments/ui An error occurred, please contact your workshop proctor or raise an issue at https://github.com/aws-samples/eks-workshop-v2/issues The full log can be found here: /eks-workshop/logs/action-1738100523.log

What did you expect to happen?

prepare environment OR delete-environment -No Timeout should occur

How can we reproduce it?

ec2-user:~/environment:$ prepare-environment

Anything else we need to know?

No response

EKS version

latest

[Supreeth095]

NOTE: This looks super Similar to "https://github.com/aws-samples/eks-workshop-v2/issues/1062"

[niallthomson]

Hi @Supreeth095 what lab were you doing when you hit this issue?

[Supreeth095]

I don't remember, most likely Security or Networking..!

But After this, nothing seems to work. I even tried deleting my cluster and starting afresh, even the cluster creation failed for some reason..!

[Supreeth095]

FYI: Using cluster.yaml from main branch of git repo (Jan 27) fixed the issue for me as well.

[cskalyan]

I provisioned the cluster using terraform and trying Load balancers lab and running into this same issue.