squakez commented on issue #5898: URL: https://github.com/apache/camel-k/issues/5898#issuecomment-2434330448
Thanks for testing. Then, it seems to be some kind of problem with the either Kubernetes or the registry itself. I suggest running two additional tests to verify where the problem happen. 1. Try to run the kit from an external Pod and using the private secret. You can follow the guidelines in https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret - use the image "redacted.io/camel/camel-k-kit-csbbtv5qhr6c73at2ta0@sha256:efabd03db8c9df31e6b8e7454a47e2a7986cc6a7dc482533d2c2075c5494a642". 2. Try to use an alternative registry just for the sake of testing. Most of our verification are done against Docker Hub using the [pull secret configuration guide](https://camel.apache.org/camel-k/next/installation/registry/registry-secret.html) - having some other registry tested would be good to understand if the problem is on the registry side. Please, reports the outcome so we can see how we can keep helping. The real strange thing is that the same mechanism works fine with push but not with pull. You may also want to check any particular requirements needed on the registry (ie, the registry may be configured to push but not to pull?). For instance, I can see the [GitHub package registry](https://camel.apache.org/camel-k/next/installation/registry/special/github.html) requires the user to configure either read or write operations: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
