Hi Sato, Thanks for the info!
So from a base it looks like what we want to achieve. However our requirement is a little bit different as we need to stage to another cluster. Thus following questions: - Would it in theory work just to stage the Integration and IntegrationKit CR ? (assumption: image registry is shared, all traits and kamelets are available on the target cluster) Or would be the correct way - as written in the linked github issue - to just stage the Integration CR and use the container.image trait to ensure that the tested image is reused? Regards, Christoph -----Original Message----- From: Tadayoshi Sato <sato.tadayo...@gmail.com> Sent: Thursday, 18 August 2022 06:49 To: users@camel.apache.org Subject: [EXTERNAL] Re: Staging of Camel-K Integrations - Best Practices ? Hi, In the upcoming Camel K 1.10.0 release we will add a new command `kamel promote <integration>`, which should be essentially what you are looking for. It does promote the integration and image build tested in a dev namespace to a prod namespace. https://github.com/apache/camel-k/pull/3325 The documentation is still to be done. On Wed, Aug 17, 2022 at 12:21 AM Christoph Weiss <christoph.we...@de.ibm.com> wrote: > Hello, > > I am looking for “best practices” to stage a Camel-K Integration > across multiple environment (e.g., Test, PreProd, Prod). > > My primary goal is to have only one “image build” (and not one per stage). > My current understanding is that I would need to stage the > Integration and IntegrationKit C (config per stage via configmaps / secrets). > Is this correct? And most important: would this work? (not sure how > the operator behaves). > > Any other “best practices” that should be followed? > > Any hints are welcome. Cheers Christoph > -- Tadayoshi Sato
