aws-samples / aws-samples/cdk-eks-karpenter
Helm upgrade for karpenter version 0.37.0 is failing with context deadline exceeded.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
When I am trying to upgrade karpenter version from v0.29.1 to 0.37.0 I am getting context deadline exceeded error.
```
Received response status [FAILED] from custom resource. Message returned: Error: b'Error: UPGRADE FAILED: context deadline exceeded\n'
```
I even tried to upgrade to 0.33.1. Facing the same issue.
We guess the helm chart upgradation is taking more time than expected but not very sure.
Is there anyways we can solve this issue? Can we increase the timeout time for helm upgrade?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing a Helm upgrade from Karpenter v0.29.1 to v0.37.0, then compare the failure with the attempted v0.33.1 upgrade and inspect the custom-resource response. Done means identifying the timeout cause and confirming a reliable upgrade path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes, typescript
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100