nicolaferraro commented on issue #2485: URL: https://github.com/apache/camel-k/issues/2485#issuecomment-875588689
So, technically the pull secret is stored on the namespace and it should be shared among all nodes, so if a node is deleted and the pod (here we are in the Kubernetes domain, the Camel K operator should not interfere with that behavior) recreated on another node, the same pull secret used by previous node should be used by the new one. So I assume you're currently not using them but want to.. The trait you've configured should be correct. Did you try to apply that configuration upon creation of the integration, e.g. using `-t pull-secret.enabled=true -t pull-secret.secret-name=registry` ? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
