关于FIS 2.0支持camel-spark-rest及迁移风险的技术问询

Hey Lan, great question—let's break this down clearly for you.

First, the core answer: You can technically run camel-spark-rest in your Spring Boot-based FIS setup (as your test proves), but there are critical, unspoken risks tied to the official "unsupported" label you need to account for.

Why the docs flag it as unsupported #

The Red Hat FIS 2.0 documentation explicitly calls out camel-spark-rest as an unsupported starter module due to compatibility concerns:

Unsupported Starter Modules
The following components do not have a starter because of compatibility issues:
...
camel-spark-rest
...

This doesn't mean the component is broken—it just means Red Hat won't stand behind it with official support, bug fixes, or compatibility guarantees for FIS and OCP environments.

Key potential risks to consider #

Here's what you might run into if you proceed with using camel-spark-rest in production:

• No official support: If you hit bugs, performance bottlenecks, or conflicts with other FIS/OCP components, Red Hat won't troubleshoot or patch these issues for you. You'll have to rely on community forums or your own debugging work to fix problems.
• Hidden compatibility gaps: The "compatibility issues" cited in the docs might not show up in your local Spring Boot test, but could surface in OCP production. For example: conflicts with OCP's network policies, dynamic port rules, or FIS's integrated runtime layers.
• OCP environment mismatches: Your current config hardcodes port 9091, but OCP uses dynamic port allocation (via the PORT environment variable) for pods. Hardcoding ports can lead to deployment failures or services that can't be accessed via OCP routes. Additionally, camel-spark-rest's network model might not play nicely with OCP's pod networking or service exposure rules.
• Upgrade headaches: When you update FIS or OCP versions, camel-spark-rest might break due to dependency shifts or API changes. There won't be official migration guides or patches to help you resolve these issues.

Recommendations #

If this is for a production environment, I'd strongly recommend switching to an officially supported REST component for FIS, like camel-servlet or camel-undertow—these are fully tested with FIS and OCP, and come with Red Hat support to back you up.

If you absolutely need to use camel-spark-rest, make sure to:

1. Test thoroughly in a staging OCP environment (not just local Spring Boot) covering network access, high concurrency, and failover scenarios.
2. Adjust your config to use OCP's dynamic ports instead of hardcoding 9091.
3. Prepare to maintain the component yourself, including managing dependencies and troubleshooting any issues that arise.

Your sample camel-context.xml for reference:

<restConfiguration component="spark-rest" port="9091"/>
<rest id="_rest_prj1" path="/prj1">
  <post consumes="text/xml" id="_rest_prj1_svc1" produces="text/xml" uri="/svc1/a1">
    <to uri="seda:preprocessor"/>
  </post>
</rest>

内容的提问来源于stack exchange，提问作者Lan