[CAMEL-21365] camel-jbang - Fix Kubernetes manifest generation for OpenShift - ASF JIRA

Attach files

Attach Screenshot

Add vote

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Open
Priority: Minor
Resolution: Unresolved
Affects Version/s: 4.8.0
Fix Version/s: 4.10.0
Component/s: camel-jbang
Labels:
None

Estimated Complexity:
Unknown

Description

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.