Replies: 1 comment
-
I'm not sure what exactly this means. The last part of the error suggests that your registry is using some unsigned or invalid certificate. That would be a bit weird it you used it with some public registry such as Docker Hub, Quay or the GitHub. But assuming you are on Kubernetes, I guess you can try this option: https://github.com/GoogleContainerTools/kaniko#--insecure ... you can set it in the https://strimzi.io/docs/operators/latest/full/using.html#type-DockerOutput-reference |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I am deploying strimzi kafka-connect with 2.7.0 and operator version 0.23. While deploying kafka connect with 3 replicas build failing due to following issue. I have tried for both public and private repositories, for both build is failing. Any suggestions in configurations will be helpful. Providing configurations of kafka-connect in below file. Thanks.
kafka-connect-config.txt
kafka-connect-build pod logs:
-->kubectl logs my-connect-cluster-connect-build -n kafka-ethonag
error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "/strimzi-kafka-connect-ng-post:2.7.0": creating push check transport for : Get "/v2/": x509: certificate signed by unknown authority
Beta Was this translation helpful? Give feedback.
All reactions