Replies: 1 comment
-
hi @burrmit I haven't looked deeply into why setting the TLSClientConfig doesn't work, but will investigate further. Thanks for raising the issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am running into a problem ever since attempting to upgrade from version 2.7 to (i have tried 3.3/3.4/3.5) and getting the same results.
I think it might have something to do with my cosign validator, but not 100% sure.
After what appears to be a successful installation, connaisseur is properly denying images that do not match my policy that has been configured:
Error from server: admission webhook "connaisseur-svc.lab-connaisseur-ns.svc" denied the request: No matching policy rule could be found for image docker.io/library/redis:latest.
However, my images that should match the policy configured are just timing out:
Error from server (InternalError): Internal error occurred: admission plugin "MutatingAdmissionWebhook" failed to complete mutation in 13s
When looking through the logs I am seeing this error message (this is with version 3.3.0):
When running version 3.5.0 I see this in the logs for images that should match the policy:
Both version throw the same failed to complete mutation and not sure what I am missing.
here is a redacted version of my values.yml
So I believe I have narrowed it down now more, and it looks to be related to certificates; however, the cert section in the values file was working just fine in previous version of Connaisseur, and now it seems to not be validating the same certificate that as not changed, in the later versions.
Error being seen now after turning off the
verifyInTransparencyLog: false
flag (required because we are using Cosign 1.0 for signing, is this:Beta Was this translation helpful? Give feedback.
All reactions