timothydilbert commented on issue #4130: URL: https://github.com/apache/camel-k/issues/4130#issuecomment-1471141392
No use case justifying not having an image registry configured in OCP. In my opinion, the error message is misleading and doesn't point to the direct issue, which is that the internal registry was not configured, and that is a requirement in order to deploy a KameletBinding. I'm raising this issue because newcomers (who might have deployed OCP just to test Camel-K) might miss the step to configure the internal registry, thus running into this exact error message. When installing the Camel-K Operator (or while deploying the KameletBinding) there should be some business logic that checks the status of the internal registry. If not configured, you should not be able to deploy KameletBindings. This business logic will prevent further Red Hat tickets/Github Issues when future developers interested in Camel-K run into the same problem, and are configured and misled by an error unrelated to Camel-K but instead related to unfinished OCP deployment, exactly like I did. -- 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
