image-automation-controller
image-automation-controller copied to clipboard
fluxcd
GitOps Toolkit controller that patches container image tags in Git
Consider following workflow: * Create a tag `v1.0.0` and push * CI builds an image and add it to a registry server. * GitRepostory scans for `semver: >=1.0.0 =1.0.0
I figured it'd be more polite to open a new issue about this rather than spawn two conversations from #164 so I'm quoting from that. >> For example, if I'm...
I upgraded to 0.13 and as such migrated our `ImageUpdateAutomation` object to `v1apha2`. However, seeing some strange behavior. Before this update, the controller would respect the `interval` I set of...
Image markers cannot be emitted by configuration transpilers like jsonnet, because they are comments in yaml files. In our case this makes the migration from flux v1 nearly impossible, because...
When replacing images in a workload, it'd be good to keep the format that the workload itself uses, and just replace the tag (or digest, if that's supported). E.g., if...
### Describe the bug Blank lines are removed from my kustomization.yaml after an image update. In large kustomizations it useful to seperate sections for readability. ### To Reproduce Start with...
Hi all, First of all, thanks for the work. I am using the latest version of Flux2 and image-automation-controller / reflector. Given the following resources: ```yaml --- # Source: environment/templates/env-sync.yaml...
Sometimes people want to use the image digest rather than (or as well as?) the tag. Assuming https://github.com/fluxcd/image-reflector-controller/issues/87, this controller could add extra setters for the digest (e.g., `sha256:abc123...` of...
Not sure how relevant these are, since envtest is pretty viable. But at least think a bit about it ...
### Discussed in https://github.com/fluxcd/flux2/discussions/3027 Originally posted by **tun0** August 24, 2022 The notifications we currently have with Flux v1 (with help of fluxcloud) mention both old and new image tags....
