jamesnetherton commented on code in PR #27863:
URL: https://github.com/apache/camel/pull/27863#discussion_r4280672045
##########
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_24.adoc:
##########
@@ -88,6 +88,30 @@ artifacts, so either the ArangoDB driver or the other
components fail at runtime
driver maintainers is to replace `com.arangodb:arangodb-java-driver` with
`com.arangodb:arangodb-java-driver-shaded`,
which embeds its own relocated copy of Vert.x. The `vertx` option of
`camel-arangodb` cannot be used in that case.
+=== camel-kubernetes - Kubernetes client 8
+
+`camel-kubernetes` now uses the fabric8 Kubernetes client 8.0, which brings
these changes for applications:
+
+* The client uses its Vert.x 5 HTTP client
(`io.fabric8:kubernetes-httpclient-vertx-5`) instead of the Vert.x 4 one
+ (`io.fabric8:kubernetes-httpclient-vertx`). An application that excludes the
default HTTP client, for example
+ to use OkHttp or the JDK HTTP client, must now exclude
`kubernetes-httpclient-vertx-5`.
+* The client and its model use Jackson 3 (`tools.jackson`). Jackson 2 does not
apply the serializers of the
+ model, so Kubernetes model objects serialized with Jackson 2 come out in a
different shape. For example, a
+ `targetPort` of `8080` is written as `{"value":8080,"intVal":8080}`, and a
CPU limit of `500m` as
+ `{"amount":"500","format":"m"}`. This affects routes that marshal the result
of a `camel-kubernetes` producer
+ with the `camel-jackson` data format (`marshal().json()`), and application
code that uses its own Jackson 2
+ `ObjectMapper`. Replace the `camel-jackson` dependency with
`camel-jackson3`, which provides the same `jackson`
+ data format on Jackson 3 (see
xref:components:dataformats:jackson3-dataformat.adoc[JSON Jackson 3]), so the
route does not
Review Comment:
Thanks, fixed in 3d748e1.
_Claude Code on behalf of @jamesnetherton_
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
