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
