Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm Chart doesn't honor Templates folder #1489

Closed
NArnott opened this issue Mar 8, 2021 · 1 comment
Closed

Helm Chart doesn't honor Templates folder #1489

NArnott opened this issue Mar 8, 2021 · 1 comment
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/duplicate This issue is a duplicate of another issue
Milestone

Comments

@NArnott
Copy link

NArnott commented Mar 8, 2021

When installing the following helm chart using Pulumi, it installs more than it is supposed to: https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller

The chart has both a templates folder, and a crds folder. The Helm CLI only installs yaml files defined in the templates folder. Pulumi, for some reason, is also including yaml files defined in the crds folder, which is incorrect.

You'll notice in the git repo that if you scroll down, the instructions ask you to apply the crds yaml files manually before using the helm chart, which I do using a ConfigGroup. However, as part of the helm chart, Pulumi then tries to run the crds/*.yaml files again, causing a conflict and failure.

I confirmed that the Helm CLI does not include the crds folder, as expected, by running the Helm Template command (which doesn't include that folder's yaml files.

I've been waiting a long time to be able to apply this using helm inside Pulumi (now that pulumi/pulumi#4224 as been resolved), but now hit this roadblock.

@NArnott NArnott added the kind/bug Some behavior is incorrect or out of spec label Mar 8, 2021
@leezen leezen added kind/bug Some behavior is incorrect or out of spec and removed kind/bug Some behavior is incorrect or out of spec labels Mar 9, 2021
@leezen leezen added this to the 0.56 milestone Apr 28, 2021
@viveklak viveklak added the resolution/duplicate This issue is a duplicate of another issue label May 12, 2021
@viveklak
Copy link
Contributor

This is because of the behavior described in #1195 and the fix for that in #1572 should fix this as well. Closing as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants