Dynamic Args ? #75
-
Just watched the kluctl hands-on introduction on Rawkode (https://youtu.be/9LoYLjDjOdg) and was impressed with the tool. I never really liked HELM but so many charts to ignore them. In the past I have manually helm templated them and used kustomize to overlay changes. This gave me the advantage of git diffs between versions but also the concept of environments albeit with kustomize overlays which are not ideal. Klutctl solves this in a nice way and also solves my OCD on GO templating being ugly, always felt Jinja was nice looking and logic. So thanks. Kudos aside, looking at the documentation (https://kluctl.io/docs/reference/deployments/deployment-yml/#args) it doesn't mention anything about having to define a variable as a dynamic argument in order to inject it via the CLI. As can be seen below when I comment out the dynamicArgs definition I can no longer use the variable args.workers in my templates. So just wondering if this is expected behavior or I am doing something wrong. If this is expected behavior what is the design decisions around this for my understanding. It just is a bit painful to have to define the dynamic argument for every target you have. If this is a security feature would be good to potentially allow someone to override this default behavior. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
As this removes the initial reasons for |
Beta Was this translation helpful? Give feedback.
dynamicArgs
is a relict from an older incarnation of kluctl. In the past, we had a proprietary controller running in our clusters that allowed to remotely trigger deployments and override args while doing this. As a security measure, I limited overriding to args that got explicitly allowed viadynamicArgs
. This proprietary controller is dead now and the open source flux-kluctl-controller will never have such a feature (a rest api to trigger deployments) and instead fully rely on CRDs/CRs.As this removes the initial reasons for
dynamicArgs
, I finally decided to ditchdynamicArgs
in a future release. 2.16.0 will already deprecate it via #71 (48cf6db to be specific) which will then cause kl…