ChrWeissDe commented on issue #3662:
URL: https://github.com/apache/camel-k/issues/3662#issuecomment-1256925665
Hi @heiko-braun sure
I hope the following explanation clarifies the requirement:
First we have the requirement to store all used "Kubernetes Custom
Resources" - in this case e.g. the Integrations, Kamelets, required ConfigMaps
and co within a "company wide central" artifact repository.
From the there artefacts are deployed to the different Kubernetes stages -
e.g. test, pre-prod (qs) and prod.
On the stages itself the CRs will be handled by a (pre-installed) Camel-k
operator.
The second requirment we have is that all artefacts - which are stored in
the artifact repository - must (!) be build on a central company wide build
plattform. This is actually a dedicated plattform - managed by a central team
(classic approach - no DevOps ; ) .
In general we have the option to install on the plattform additional
required (simple) tools on the build platform. E.g. specific C or Java compile
version or a Camel K CLI. However the need of a fedicated Kubernetes Cluster
just for the build is seen as "complex" (in terms of setup and manage this
cluster).
Thus it would be really beneficial to be just able to use "kamel run" to
create the CRs - without a cluster.
Further: I see the requirements also by a couple of other customers- as
especially large customer are still running a central build plattform.
The build - in this case the creation of the Camel-K CR - needs to be done
on a central Build Server.
--
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: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
