aws-samples / aws-samples/eks-workshop-v2
[Bug]: Error deploying Argo CD Lab
- Dominant language
- HCL
- Stars
- 626
- Forks
- 613
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 9
Description
### Installation method
Workshop Studio
### What happened?
Running the `prepare-environment automation/gitops/argocd` I'm getting timed out errors for some pods:
```
timed out waiting for the condition on pods/catalog-759cdd5598-k5gqk
timed out waiting for the condition on pods/catalog-mysql-0
timed out waiting for the condition on pods/checkout-9cc47f6f4-vw4r4
timed out waiting for the condition on pods/checkout-redis-5df64d4f66-62w9t
timed out waiting for the condition on pods/orders-5c597c5965-ckm6p
timed out waiting for the condition on pods/orders-mysql-5dcdcccbf9-5jvrh
timed out waiting for the condition on pods/ui-68495c748c-s9whs
```
### What did you expect to happen?
Prepare step should run successfully
### How can we reproduce it?
Run the preparation step `prepare-environment automation/gitops/argocd`
### Anything else we need to know?
`carts` and `catalog` pods are in `CrashLoopBackOff`
Also one of the `coredns` in one node is not running
### EKS version
1.29
Contributor guide
Research direction
Start by running `prepare-environment automation/gitops/argocd` in the Workshop Studio setup and inspect the listed pods, including `carts`, `catalog`, and `coredns`. Compare pod events and logs against the EKS 1.29 environment; done means the preparation step completes without pod timeouts or CrashLoopBackOff failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100