uderik

@stefanprodan we also really need this enhancement, we have many environments and would like to somehow identify them, only for production 6 dedicated clusters

I have not found a normal solution to send messages only for new image releases via alert, ImagePolicy spam message on every scan

@pjbgf 0.23.5 works fine 0.24.1/0.24.0 versions does not work, crashing after start

Hello @kingdonb last working version 0.18.0, after upgrade to 0.19.0 got: `Head "https://my-gitops.s3.dualstack.us-east-1.amazonaws.com/": context deadline exceeded` update to latest version flux (0.26.0) with fluxcd/source-controller:v0.21.1, problem still present it's standard AWS...

@hiddeco >2 minutes for reconciliation source-controller v0.21.1 :'( .spec.timeout = 4m ``` ❯ time flux reconcile source bucket my-gitops ► annotating Bucket my-gitops in flux-system namespace ✔ Bucket annotated ◎...

Hi @stefanprodan , what needs to be done for this PR to be accepted?

@jmdeal When I try to launch an instance using a snapshot, Karpenter doesn't apply tags to the instance itself, which leads to the following error from AWS: ``` { "allowed":...

All the necessary tags are specified, and there are no issues when launching instances. However, when I specify snapshotId for EBS, I get the error that I mentioned above.

Same issue persists after switching from the Bitnami external-dns Helm chart (external-dns:0.17.0-debian-12-r5) to the upstream external-dns chart (v0.19): After removing all existing DNS records, external-dns recreates A records without the...