image-automation-controller
image-automation-controller copied to clipboard
fluxcd
GitOps Toolkit controller that patches container image tags in Git
### Describe the bug image-automation-controller crashing. See below. ### Steps to reproduce Can not reproduce at will. This happens about once per week or so. Note: Flux actually behaves as...
image-automation-controller v0.24.1 crash loop after update to latest version log attached [image-automation-controller.log](https://github.com/fluxcd/image-automation-controller/files/9311074/image-automation-controller.log)
I have an issue with updating image due to the mixed naming of tag which contained both numbers and letters (I'm using `CI_COMMIT_SHORT_SHA` once pushing new image to repo in...
The controller is intermittently experiencing a crash during a libgit2 Fetch operation: ``` fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x1 addr=0x636365207d pc=0x1a2372e] runtime stack: runtime.throw({0x1e28bd7?,...
Running all CI tests at pull requests for some files are not as relevant as to others. For example, release PRs contains changes to CHANGELOG.md only, and none of the...
Add persistent storage / caching mechanisim We have quite a bit of repository and it seems that the ImageUpdateController does a lot of data transfer (maybe due to some configuration...
Intermittently a data race is being detected when running the controller's tests: ``` ================== WARNING: DATA RACE Write at 0x00c000a63dc0 by goroutine 88: github.com/fluxcd/source-controller/pkg/git/libgit2/managed.(*sshSmartSubtransport).Close() /home/runner/go/pkg/mod/github.com/fluxcd/[email protected]/pkg/git/libgit2/managed/ssh.go:314 +0x97 github.com/fluxcd/source-controller/pkg/git/libgit2/managed.(*sshSmartSubtransport).Action.func3() /home/runner/go/pkg/mod/github.com/fluxcd/[email protected]/pkg/git/libgit2/managed/ssh.go:252 +0x325 github.com/fluxcd/source-controller/pkg/git/libgit2/managed.(*sshSmartSubtransport).Action·dwrap·2()...
Hi there, In our environments we use Flux's image automation solution to automate delivery of the new software versions with the following setup: Gitlab container repo > Flux image repository...
I have the following setup: Flux2 is running in namespace `flux-system`. Prometheus is running in namespace `monitoring`. I am trying to get image automation to work with as little duplication...
Image Automation Controller does not have a `Spec.Timeout`, as most other controllers do, instead it applies the `Spec.Timeout` set in the referred source, and uses that timeout for each Git...