John Jeffers

Well damn, it looks like there's an existing `.gitleaks.toml` in the repos where it's failing. So I'm sure that must be the problem. Sorry to bug you, and thanks for...

> The solution above used drive on version 1.8. The latest version of the drive, 1.10, has already fixed the issue. It's definitely not fixed in 1.10. I have 1.10...

Could we please get an update on why this is taking so long to fix? All that has to be done is update the toleration on the daemonset to ```...

OK just to make sure I understand, the permanent fix for this is in the backlog so we won't see it for a while, but if I manually update the...

Any progress on this? It would be extremely helpful!

We suspect it was malformed YAML. Here's a sample: ``` apiVersion: apps/v1 kind: Deployment metadata: name: my-app namespace: my-app labels: app: my-app team: ops environment: stg spec: replicas: 1 selector:...

I'd like to know how to do this as well. I looked thru the docs and examples, and the linked PR, but I don't see anything that explains how to...

@jlbutler I agree that it's good to be able to see the untagged images but it's a lot of visual clutter when most of the time you just want the...

Is there any timeline/estimated release date for v20.0.0? EKS 1.29 has kinda forced my hand on dealing with Karpenter. ``` ERROR controller.awsnodetemplate karpenter version is not compatible with K8s version...

@bryantbiggs Thanks for that info. I know that the module isn't the reason for the error message. What I didn't know is that Karpenter 0.33 isn't compatible with k8s 1.29....