Nuru
Nuru
Closing, because we are not going to add this feature for reasons explained [above](https://github.com/cloudposse/terraform-aws-tfstate-backend/pull/176#issuecomment-2244532640).
@mumoshu I could use an option for `skip-crds`, preferably in the helmfile as with `createNamespace`. ``` helmfile sync --args --skip-crds ``` is a problem, because I need it for `helm...
@mumoshu If we want to manage CRDs some other way than with the helm chart we are using to install the program, `--skip-crds` keeps helm from doing anything with them....
> @Nuru Thanks! Gotcha. So you would probably like to use it from a command-line arg, like `helmfile sync --skip-crds`, right? There will be no use-case if we make it...
@mumoshu This is a bigger problem than I thought, because I cannot use `helmfile apply --args --skip-crds` because of `helm diff`.
@ellistarn I disagree, also. The Getting started guide just says to create an IRSA, it does not specify what policy to create or even give a reference to where to...
@ellistarn Can you add a label or something to keep this issue from auto-closing while you work on it?
@chrisnegus Thank you for the documentation. The explanations of why Karpenter needs what permissions, and commentary on what the permissions actually grant, are very helpful. Nevertheless, I'd ask you to...
> Hey @Nuru, looks like the [initial block](https://karpenter.sh/preview/reference/cloudformation/#karpentercontrollerpolicy) for the controller policy is in CFN, but each of the required policies are in JSON. Are you able to conjoin these...
Closing as not helpful