You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Christoph Deppisch (Jira)" <ji...@apache.org> on 2024/07/30 19:10:00 UTC
[jira] [Updated] (CAMEL-20985) camel-jbang: Kubernetes plugin: Support Camel K integrations and pipes in export
[ https://issues.apache.org/jira/browse/CAMEL-20985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Deppisch updated CAMEL-20985:
---------------------------------------
Fix Version/s: 4.8.0
(was: 4.x)
> camel-jbang: Kubernetes plugin: Support Camel K integrations and pipes in export
> --------------------------------------------------------------------------------
>
> Key: CAMEL-20985
> URL: https://issues.apache.org/jira/browse/CAMEL-20985
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
> Reporter: Christoph Deppisch
> Assignee: Christoph Deppisch
> Priority: Major
> Fix For: 4.8.0
>
>
> The Camel JBang Kubernetes plugin is able to leverage the trait configuration options to generate a Kubernetes manifest during export.
> The plugin should support Camel K integrations and pipe resources as source of export. The integration and pipe may use trait configuration as part of the specification. These trait config options can be directly used to generate the Kubernetes manifest.
> This way users should be able to generate an arbitrary Quarkus/SpringBoot project with a normal Kubernetes manifest from the Camel K integration or pipe. The result can be deployed to a cluster where the Camel K operator is not present for some reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)