Luke Arntz
Luke Arntz
There are critical CVEs in the argocd-image-updater container. Image tagged [v0.12.0](https://quay.io/repository/argoprojlabs/argocd-image-updater?tab=tags). Most of these have been fixed; see [here](https://quay.io/repository/argoprojlabs/argocd-image-updater/manifest/sha256:27825f32240aadde43ea3c3eb2f37b2e98086df9d83e5fbbb0e41c6c0cec0cf1?tab=vulnerabilities) and [here](https://quay.io/repository/argoprojlabs/argocd-image-updater/manifest/sha256:b2b12f932b9d957a1d415f8edcae179834e8db3f19b19e6efb6b0af7d02a1097?tab=vulnerabilities)  --- Hello, Our security team is asking us...
I am using the terraform provider to manage a few projects in atlas. I was able to use this exact terraform on another project earlier today, but on this one...
Today I updated flux (v2.1.1 -> v2.2.2) in a cluster and one of our HelmRelease's was unexpectedly uninstalled/installed. We tracked this down to a change in `targetNamespace`, and now know...
### Issue https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/3649 ### Description There is a similar [pr](https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/3675) open for the kubernetes libs, but there haven't been any updates in a few weeks. In the comments of that...