Alexander Block

@jcpunk Independent from the feature request in this issue, it looks like you're "overusing" args a lot. They are meant as an "entrypoint" into configuration, while the actual configuration is...

I was not aware that this is possible in Helm and agree that this should be supported by Kluctl as well. I believe this is mid-sized task that could easily...

@chiragbhatia8 Happy to see you working on this :) If you need help, contact me either here or via the CNCF Slack (kluctl channel).

@mirsafari Yes, the long-term goal is to show all fields unknown to kluctl that were added by an external source. So your example would be covered as well. I plan...

#289 will add `skipPrePull` to `helm-chart.yaml`, which at least implements parts from this issue. I started implementing templating support for versions and repo urls and realised that it would make...

Implementing this feature is something I planned for a long time already but never found the time to actually do it. I hope I can put this into v2.21 or...

:+1: for the idea of exposing context information about the current deployment project as variables. I'd suggest the following structure. The root variable exposed per deployment item would be `deploymentItem`....

@MarkCupitt Thanks for the feature request. Can you check if this is maybe a use case for a [kluctl hook](https://kluctl.io/docs/kluctl/reference/deployments/hooks/) + Job? This is what we usually do if need...

Can't provide a fully functional example atm, but something like this should work: ```yaml apiVersion: batch/v1 kind: Job metadata: name: "create-users-job" annotations: kluctl.io/hook: post-deploy,post-deploy-initial kluctl.io/hook-delete-policy: before-hook-creation spec: template: metadata: name:...

We clearly need better documentation for this feature as it's one of the most important feature to get sane and reliable deployments working.