lburgazzoli commented on issue #5112:
URL: https://github.com/apache/camel-k/issues/5112#issuecomment-1930342054
> Also changing from using the naming convention of the image to the fact
that we have an external kit would just disable the workaround given by the
naming convention check.
still, I think that we should remove the container image name check as it is
redundant and not in line with the design principle of the `IntegrationKit`.
> The operator cannot know for sure if a container was created by the user.
Yes for an external integration kit we should assume that the container
image has a proper entrypoint and disable some traits such as the jvm one (and
maybe some others)
The proper way for reuse a container image should be to also copy the
related `IntegrationKit` and instruct the integration to use it.
--
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]
