pealtrufo

Hi. I am experiencing same issue here.

Hi @chipzoller I have tested @galsolo's suggestion using kyverno 1.8.0 with this outcome: ``` verify-image: autogen-verify-image: |- failed to verify image .dkr.ecr.eu-west-2.amazonaws.com/image:tag: .attestors[0].entries[0].keys: no matching signatures: getting public key: operation...

Hi @shahpratikr Thing is that I don't have credentials to provide. I only have roles to assume. Personally, I don't think provisioning AWS creds to kyverno pod that way is...

Hi @shahpratikr Just to confirm I understand the approach you're suggesting. Do you mean adding those files to Kyverno's pod? @chipzoller, I think the point I was trying to make...

Hi. Is there any plan to add GitLab support? Considering the age of this request I suppose there isn't, but thought about asking just in case. I've tested it in...

Hey @fjogeleit, there's this link to Security Hub API reference: https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html I am not very familiar with it either myself. I've seen [Trivy](https://github.com/aquasecurity/trivy) does support integration with Security Hub, and...

Hey @eddycharly This works ok in 1.7.3 Thanks

Thanks @chipzoller. This is nothing related to TLS certs self-signed though. I am using a private ECR registry in my AWS account. Kyverno can reach it, but needs credentials to...

Hi @JimBugwadia I don't think the solution provided by @patelrit above deliver the enhancement requested in this issue. It would work, but I thought the ideal solution was having a...

Thanks @JimBugwadia I did try to configure the SA with the right IAM permission but couldn't make it work. Current implementation only supports imagePullSecret for this, right? The reason I...