Closed kol-ratner closed 8 months ago
Flux can only update plain Kubernetes YAML which are stored in Git, adding a comment to objects in etcd will not do anything. Flux can't work with CUE files or Helm templates or any other format besides Kubernetes YAML. I'm also confused about what are you trying to achieve.
hi @stefanprodan thanks for your response - to clarify my use case:
I am running timoni to build my k8s application manifests and am running fluxv2 to manage the cluster.
at present when we want to deploy a new application container image version we must manually update the image tag in the cue based values file.
i would like flux to watch the container registry and update the lastest deployed image. Ive been attempting to use flux's ImageRepository
/ ImagePolicy
resources to handle this.
At present, I do understand that this wont work without flux's ImageUpdateAutomation
resource, however flux cannot edit cue values files in my git repo.
Is it feasible to write a cue parsing tool which can update my cue values file and have it triggered by flux's ImagePolicy
which is configured to watch the container registry... ?
Zooming out: do u have a general recommendation, given our current usage of timoni and flux on how to automatically update the deployed version of an application container image?
Flux does not update things in-cluster, the image automation is pushing file changes to Git. Even if you would use Timoni Bundles in YAML format, you still need some other automation in CI to rerun the timoni push command.
hi @stefanprodan loving timoni, having an issue with automation of image updates by flux,
following along here: https://fluxcd.io/flux/guides/image-update/#configure-image-updates
and its not clear to me how i might be able to add the required marker comment to my deployment:
i have an included a naive attempt to add a comment to the image reference, it does not seem like the correct way to go about this given the following error from flux:
my deployment.cue file is as follows