This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/main by this push:
new 37397908ee Fix integration cassandra-source kamelet pod status is in
running state but not ready
37397908ee is described below
commit 37397908ee504d440fe0632e3b9c2f635f27da7a
Author: JinyuChen97 <[email protected]>
AuthorDate: Mon Aug 10 11:00:12 2026 +0100
Fix integration cassandra-source kamelet pod status is in running state but
not ready
---
docs/modules/ROOT/pages/migration-guide/3.39.0.adoc | 15 +++++++++++++++
.../ROOT/pages/reference/extensions/cassandraql.adoc | 12 ++++++++++++
.../cassandraql/runtime/src/main/doc/configuration.adoc | 11 +++++++++++
3 files changed, 38 insertions(+)
diff --git a/docs/modules/ROOT/pages/migration-guide/3.39.0.adoc
b/docs/modules/ROOT/pages/migration-guide/3.39.0.adoc
index a4462f9a7e..26f57a8144 100644
--- a/docs/modules/ROOT/pages/migration-guide/3.39.0.adoc
+++ b/docs/modules/ROOT/pages/migration-guide/3.39.0.adoc
@@ -35,3 +35,18 @@ quarkus.camel.jolokia.remote-access-allowed=true
----
This is safe when combined with SSL client authentication (enabled by default
in Kubernetes environments), which ensures only clients presenting a valid
certificate can connect. Refer to the
xref:reference/extensions/jolokia.adoc[Jolokia extension documentation] for
full details.
+
+== CassandraQL extension
+
+=== Cassandra health check may cause pod readiness failures
+
+The `cassandra-quarkus-client` dependency used by the CassandraQL extension
automatically registers a health check that connects to the Cassandra instance
configured via `quarkus.cassandra.contact-points`. Since Camel manages its own
`CqlSession` independently, this property is typically not set, causing the
health check to default to `127.0.0.1:9042` and fail. This results in
Kubernetes readiness probes reporting the pod as not ready.
+
+If you encounter this issue, disable the Cassandra Quarkus Client health check
in your `application.properties`:
+
+[source,properties]
+----
+quarkus.cassandra.health.enabled=false
+----
+
+Refer to the xref:reference/extensions/cassandraql.adoc[CassandraQL extension
documentation] for more details.
diff --git a/docs/modules/ROOT/pages/reference/extensions/cassandraql.adoc
b/docs/modules/ROOT/pages/reference/extensions/cassandraql.adoc
index 9c428a9e41..9c4d0b2faf 100644
--- a/docs/modules/ROOT/pages/reference/extensions/cassandraql.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/cassandraql.adoc
@@ -48,6 +48,18 @@ endif::[]
[id="extensions-cassandraql-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration
+[id="extensions-cassandraql-configuration-cassandra-health-check"]
+=== Cassandra health check
+
+The `cassandra-quarkus-client` dependency, which is used internally by this
extension, automatically registers a health check. However, Camel manages its
own `CqlSession` independently and does not use the Quarkus-managed Cassandra
client, so the health check may fail and cause Kubernetes readiness probes to
report the pod as not ready.
+
+To work around this, disable the Cassandra health check in your
`application.properties`:
+
+[source,properties]
+----
+quarkus.cassandra.health.enabled=false
+----
+
[id="extensions-cassandraql-configuration-cassandra-aggregation-repository-in-native-mode"]
=== Cassandra aggregation repository in native mode
diff --git a/extensions/cassandraql/runtime/src/main/doc/configuration.adoc
b/extensions/cassandraql/runtime/src/main/doc/configuration.adoc
index b0189c3dfd..6d27470554 100644
--- a/extensions/cassandraql/runtime/src/main/doc/configuration.adoc
+++ b/extensions/cassandraql/runtime/src/main/doc/configuration.adoc
@@ -1,3 +1,14 @@
+=== Cassandra health check
+
+The `cassandra-quarkus-client` dependency, which is used internally by this
extension, automatically registers a health check. However, Camel manages its
own `CqlSession` independently and does not use the Quarkus-managed Cassandra
client, so the health check may fail and cause Kubernetes readiness probes to
report the pod as not ready.
+
+To work around this, disable the Cassandra health check in your
`application.properties`:
+
+[source,properties]
+----
+quarkus.cassandra.health.enabled=false
+----
+
=== Cassandra aggregation repository in native mode
In order to use Cassandra aggregation repositories like
`CassandraAggregationRepository` in native mode, you must
xref:extensions/core.adoc#quarkus-camel-native-reflection-serialization-enabled[enable
native serialization support].
