(eks): deploying helm chart to cluster created in another stack fails with circular dependency #19655
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
bug
This issue is a bug.
effort/medium
Medium work item – several days of effort
p1
What is the problem?
I'm attempting to deploy a helm chart, using assets, to a cluster which I created in a separate stack. It fails with a circular dependency error due to the kubectl barrier.
I can see the original issue was addressed in #7322 with a test added for a simple kubernetes manifest. This looks to have been reverted a few months later in 4fad9bc
I'm not even sure if this should be considered a bug since that later commit quite clearly states everything should await that new barrier object. However this does to me seem to break out-of-stack helm deployments using assets. If it is the expected behaviour it'd be helpful to call it out on the
HelmChart
docs page.If this looks feature worthy (I'm not sure how feasible it actually is), let me know and I'll stick a request in.
Reproduction Steps
What did you expect to happen?
I expected to be able to deploy a helm chart from a different stack
What actually happened?
CDK CLI Version
1.149.0
Framework Version
No response
Node.js Version
16.3.0
OS
MacOs 12.3 (M1)
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: