Zach Swanson

Actually we just set `secretReader.enabled: true` in the values and redeployed (left the `secretReader.secretNames: []` as empty) and its still producing this error.

@aantn - ditto on being interested in a maintained replacement. The grafana integration for annotations sounds great.

Worth mentioning this exact problem is noted in the ArgoCD best practices as a reason to keep the app manifests and code separated - https://argo-cd.readthedocs.io/en/stable/user-guide/best_practices/#separating-config-vs-source-code-repositories

FWIW I'm not seeing any warning logs like this but we're also running image-updater 0.10.0, and the namespace is `argocd-image-updater` edit to add, I'm also not seeing events though

@DavidRileyZip I had the same issue with access denied errors, I had to allow the s3 deployment bucket for the demo to have public ACLs. Not the best setup but...

@lesh366 can you comment on the `layout` field for MS Teams from #49? I can't figure it out either.

Noted this seems resolved in the 0.10.0 release notes, but I am seeing this behavior still where a small random set of instances in the SSM Session window show up...

I will have to defer to @jonasoneves for comment on that, I'm no longer on the team using Leapp.

Seeing this in 1.7.2 I have some suspicion that its related to us not knowing how to provide the initial 'base' resource for the existing-resource (the `target` of the mutate)...

Tacking on a use-case here, we have hit a problem where an existing in-house mutating webhook and Kyverno are causing unexpected (and baffling) interactions that result in pods being unable...