squakez commented on issue #3003: URL: https://github.com/apache/camel-k/issues/3003#issuecomment-1035997580
> Hi @squakez thanks for pointing us this out. I have some questions so far > No problem, I'll try answering inline. > * Can we re-user an existing Integration Kit as it contains no sources itself? > Just copying the description of [documentation related to the IntegrationKit](https://camel.apache.org/camel-k/1.8.x/architecture/cr/integration-kit.html): "_The IntegrationKit is a fundamental side resource which describe a container image created by the camel-k operator as well as the configurations that need to be applied to every integration that is executed on top of it. An IntegrationKit does not include any source code or resource file defined by the Integration from which it has been generated._" > * Is it ok to cleanup a created Integration Kit at the k8s cluster and the dependent repository in the the registry after the build process? > In theory you should not delete IntegrationKit generated by the platform. If you run `kamel kit delete`, infact, you won't be allowed to do that. In practice, you can perform a deletion via `kubectl integrationkit delete`. While we are reasoning about the best way to garbage collect/compact interim IntegrationKit, I think you can use this strategy with the due caution. If you come out with some idea on how to perform the clean, you know, contributions are welcome. We have open a few issues around this theme: the aforementioned #2736, then #2732 and #593 > * Is it possible to perform a local build (or on a build server) upfront and deploy the built image afterwards? > I think this is something similar of what was described in #2737. > > Background of these question is that we need to have a production grade platform. Remaining Integration Kits and Repositories with no function won't even work as we're running ouf of ressources. > Yeah, it's a complex topic which need to be revisited. Thanks for popping it up. > Best Gerald -- 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]
