vponoikoait
vponoikoait
@fjogeleit in this case, maybe fields like titles itself could've be potentially configurable? What do I mean by that - in my case I can see potential combination usage ${rule_name}-${namespace}...
Current state hardly would've be usable in scale in case if there's a bigger cluster and lots of policies violation ( which shouldn't be, but lets assume somebody just added...
I would've gladly create one, but at current state I may assume it's not already fully working as potentially desired, as I have raised issue for corresponding - https://github.com/kyverno/kyverno/issues/9565 In...
According to https://github.com/kyverno/kyverno/issues/9565#issuecomment-1917044300 Actually for ClusterPolicies are always put to the default namespace, though in this case, events for the Policies can't be captured unless list option or wildcard specification...
@fjogeleit thanks a lot for the clarifications. It would be nice to have these highlighted inside of documentation itself. I will create issue later for it and in case and...
+1, great tool!
+1, I want gitleaks to ignore basically all the same files at .gitignore does
@andreasschulze you likely can try to pass config explicitly with --config and see if it works
Can see it still happening on the latest operator version in a single node setup like https://github.com/opensearch-project/opensearch-k8s-operator/issues/233#issuecomment-2779765719 opensearchproject/opensearch-operator:2.8.0 docker.io/opensearchproject/opensearch:3.1.0