I am using a customized version of the e2e.yaml workflow, but one thing I have had trouble with is how to make use of it, when the cluster I am testing makes use of more complex infrastructure e.g. cert-manager with dns01 challenges.
In those cases I am missing some way to template the clusters configuration, such that selfsigned certs and local domain names are used when running in CI. Is there someway to either edit the yaml files before flux reconciles them, or some way for the kustomization to read in external variables before reconcilitiation?
I have tried to accomplish the first need, by using 'yq' to succesfully change the yaml files to use a working configuration, but I am not able to make it apply, because flux is unable to sync from local files, and will always read the files from the git source.
Am I missing something, or have anyone else managed to create stable workflows for more complex environments?
I am using a customized version of the e2e.yaml workflow, but one thing I have had trouble with is how to make use of it, when the cluster I am testing makes use of more complex infrastructure e.g. cert-manager with dns01 challenges.
In those cases I am missing some way to template the clusters configuration, such that selfsigned certs and local domain names are used when running in CI. Is there someway to either edit the yaml files before flux reconciles them, or some way for the kustomization to read in external variables before reconcilitiation?
I have tried to accomplish the first need, by using 'yq' to succesfully change the yaml files to use a working configuration, but I am not able to make it apply, because flux is unable to sync from local files, and will always read the files from the git source.
Am I missing something, or have anyone else managed to create stable workflows for more complex environments?