Yes, we're using ArgoCD -- that's part of why I need to generate the images and object specs outside of the destination environment.
-- JCL On Tue, 20 Aug 2024, 22:46 Fabrice Martellucci, <[email protected]> wrote: > Hello, > > have you see Argo CD ? is very simple and have many pos. > > good day > > > Le mar. 20 août 2024 à 23:21, Unclear Concept < > [email protected]> > a écrit : > > > I'm hoping for some help with building a CI/CD pipeline for Camel-K > objects > > as part of KNative flows. > > > > For background: I cannot allow write access to the container repo in > PROD, > > and all deployed K8S objects must source from Git (pure gitops, so no > kamel > > CLI at deploy time). These are non-negotiable. I think I see how to > map > > from an Integration to the built container for CI, but I'm not seeing how > > to handle kamelets, or (eg) the implicit Integration for a Pipe. The > goal > > here is to have a fully disjoint CI process that (effectively) produces > K8S > > objects with versioned container references that I can deploy in PROD > > without requiring the kamel CLI etc in any way post-CI. Any pointers? > > > > I'm aware of https://camel.apache.org/blog/2023/07/camel-k-gitops/ and > > https://camel.apache.org/blog/2022/10/camel-k-cicd/ and am trying to > piece > > together a solve within the above constraints. > > > > -- JCL > > >
