astefanutti commented on issue #2358: URL: https://github.com/apache/camel-k/issues/2358#issuecomment-858654659
> Latest implementation carries through the `--registry none` and implements 3 changes: > > * platform.Spec.Registry.Address = Disabled > * platform.Spec.BuildPublishStrategy = Disabled > * platform.Spec.BuildStrategy = Disabled > > This seemed logical since the registry is required for `BuildPublishStrategy` and since one of the active types of `BuildPublishStrategy` are required for `BuildStrategy`. If this is not correct then can you provide an example please? That is correct. > If it is correct, can you provide a use-case where the operator is useful without any build capability, please? The use case it to run an Integration using a pre-built image. Obviously, this pre-built image has to comply with the Camel K runtime contract (that is not documented ;). As an easy way to write an e2e test for this, I think we could re-use any existing test, and add a subsequent test that would re-deploy the same Integration, by re-using the previously built image, and make sure both the operator installation and the Integration Pod run successfully. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
