It's mooted in https://github.com/fluxcd/toolkit/discussions/164 that a distinct metric is used for not completing reconciliation, as opposed to an unexpected error. Until that discussion has run its course, we should just do what the other controllers do, and that's returning an error when the controller is unable to reconcile to completion. This also adds a comment noting the purpose of the redundant `Requeue: true` fields, for the avoidance of confusion later. |
||
---|---|---|
.github/workflows | ||
api/v1alpha1 | ||
config | ||
controllers | ||
hack | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
DCO | ||
Dockerfile | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
PROJECT | ||
README.md | ||
go.mod | ||
go.sum | ||
main.go |
README.md
Image (metadata) reflector controller
This is an attempt to build controllers along the lines set out in https://squaremo.dev/posts/gitops-controllers/.
This repository implements the image metadata reflector controller, which scans container image repositories and reflects the metadata, in Kubernetes resources. The sibling repository image-automation-controller implements the automation controller, which acts on the reflected data (e.g., a new image version) by updating the image references used in files in git.