Paul Becotte
Paul Becotte
I don't know if this actually goes far enough. Say we have this - base --- kustomization.yaml ``` helmChartInflationGenerator: values: values.yaml patches: # some patches that I need for this...
You'll see that I wound up with the same solution...using patches on the valuesInline field to pass transformer and generator configuration up the stack. I opened a ticket related to...
I just reread my comment and realized- what I was trying to say is "multiple values files doesn't help with the hard problems - but its an easy change that...
So long as changes to the node pool don't cause the cluster to get deleted/recreated!
If you were trying to say I missed something, I said "You can add other node pools external to the cluster resource, but you can't add multiple to the cluster...
Yes, that's what I was trying to accomplish On November 18, 2023, tomlucasSQL ***@***.***> wrote: > If I understand your use case correctly, you use --load and want the >...
Looks like it hit beta in April
The helm generator in kustomize has a drastic weakness- there's no way to use kustomize patch files against the values.yaml. So I wind up with a huge copy-pasta values.yaml file...
It sorta works. It wouldn't show the relationship between the CRD object and its children, and depends on both there being nothing else in the namespace AND all the resources...
I don't think having it both ways works. OwnerReference is saying "this object created me" ... but, that's not what you're doing. If you want the Checks to belong to...