[
https://issues.apache.org/jira/browse/CAMEL-21365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21365:
--------------------------------
Fix Version/s: 4.x
(was: 4.10.0)
> camel-jbang - Fix Kubernetes manifest generation for OpenShift
> --------------------------------------------------------------
>
> Key: CAMEL-21365
> URL: https://issues.apache.org/jira/browse/CAMEL-21365
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.8.0
> Reporter: Christoph Deppisch
> Assignee: Gaelle Fournier
> Priority: Minor
> Fix For: 4.x
>
>
> When using cluster-type=openshift for the Camel JBang Kubernetes plugin
> export the resulting Kubernetes manifest is missing some information that
> causes apps to fail on OpenShift.
> We suppose that this is due to a slightly different behavior of the Quarkus
> Kubernetes extension compared to the Quarkus OpenShift extension when it
> comes to reading and merging the generated Kubernetes manifest pieces.
> This is presumably the root cause for several issues with the Camel JBang
> Kubernetes plugin when targeting OpenShift as a cluster.
> Let's make sure that the Camel JBang Kubernetes plugin generates the proper
> Kubernetes manifest so that it works with the OpenShift Quarkus extension
> just like it does with the Kubernetes Quarkus extension.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
