image-reflector-controller
image-reflector-controller copied to clipboard
fluxcd
GitOps Toolkit controller that scans container registries
# API changes In addition to the latest selected tag, ImagePolicy now allows to also record the digest of the tag in `.status.latestRef.digest`. The setting of this field is governed...
When an ImageRepository's `.spec.image` is changed to an invalid value then any refering ImagePolicy still reports success. Steps to reproduce: 1. `flux create image repository podinfo --image ghcr.io/stefanprodan/podinfo` 2. Wait...
The introduction of the `.spec.digestReflectionPolicy` field makes it necessary for the ImagePolicyReconciler to regularly reconcile ImagePolicies so that it discovers updated images independently of its accompanying ImageRepository. Some more context...
Currently the integration tests only check if ImageRepository was able to fetch tags. We should extend the tests to also create an ImagePolicy and check if they fetch the digest...
Hey there, thank you very much for you great effort with flux. Now the 'bug' :innocent: : my `ImageRepository` status looks like: ``` status: lastScanResult: latestTags: - 2.9.5 - 2.9.4...
We discovered the following issue when we used the Flux image reflector controller with JFrog Artifactory: The image controller tries to list the tags using this URL: [https://my.artifactory.com/v2/artifactory/path_to_the_tags/subpath_to_the_tags/tags/list?n=1000](url) It is...
When pushing new release tags to image repositories, it's a common practice to also update the special tag `latest` to the new release tag being pushed. It would be really...
The `image-reflector-controller` adds the following `status` to an `ImageRepository`: ``` canonicalImageName: example.com/whatnot/image conditions: - lastTransitionTime: '2022-11-09T11:59:38Z' message: 'Get "https://example.com/v2/": context deadline exceeded' reason: ReconciliationFailed status: 'False' type: Ready observedGeneration: 1...
This pull request updates the terraform files and go tests files to allow the use of Workload Identity in the azure e2e tests.
This is tad confusing: ``` jsonPayload: { ImageRepository: {2} controller: "imagerepository" controllerGroup: "image.toolkit.fluxcd.io" controllerKind: "ImageRepository" error: "Succeeded" level: "error" msg: "successful scan: found 8 tags" name: "huurwoningen-referrer-revenue" namespace: "flux-system" reconcileID:...
