timothydilbert commented on issue #4130: URL: https://github.com/apache/camel-k/issues/4130#issuecomment-1472438378
As I'm not experienced enough yet, I'm not able to comment on the difficulty/permissions required to check the internal registry. Hopefully, that changes shortly as I become more familiar with the project. If permissions/difficulty checking the internal registry is an issue. Perhaps including logic that would attempt a KameletBinding immediately after the Camel K Operator installation could be an acceptable workaround? Basically, there would be logic in the Camel-K Operator installation that would immediately try to deploy a generic (and temporary) KameletBinding. If the KameletBinding deployment fails with the same message, then you know it is because of an incomplete/unconfigured internal registry. Just offering a scotch tape solution as a last resort. Enhancing the documentation to spell that out would be good. -- 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
