Braden Wright

I'm running into this issue too, if someone got past the issue that would be great. What makes it weird is that the config was working we just added files...

I'll try upgrading and report back, right now I'm on: ``` braden@rltadmins-MBP-4 helm % helm version version.BuildInfo{Version:"v3.5.2", GitCommit:"167aac70832d3a384f65f9745335e9fb40169dc2", GitTreeState:"dirty", GoVersion:"go1.15.7"} ```

I upgraded to helm `version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.19"}` which didn't help. I've been able to fix the issue but putting the resources in top-level `crds` directory without templating as suggested...

@pdrastil the problem I see with that approach is that there isn't any guarantee that the CRD updates will occur before the custom resource is applied. I know that https://helm.sh/docs/chart_best_practices/custom_resource_definitions/...

for sure let me give that a go and see how it works, its a good suggestion

Just checking in on this

Any update on this, issue has been open over a year. Workaround gets it going but it's hacky

@chasebolt think you may have accidentally included me on this but if I'm wrong then I'd need more info. Anyways personally I don't see any problems with including it in...

fwiw I added wildcard exception b/c there wasn't a way to click it in the ui / find it for ELB / HTTP clear text. That was only a 1...

Any updates on this, I've experienced this issue as well and it would be nice to get it resolved.