Quarkus Kubernetes client bean is always injected into the Kubernetes component

[jamesnetherton]

Bug description

The quarkus-kubernetes-client extension produces a KubernetesClient which will always get autowired into the Camel component.

The downside of this is that none of the Camel component or endpoint options will have any effect by default, unless autowiring is disabled.

Potentially this is confusing UX as folks may not know that the Quarkus extension configuration is taking precedence over Camel. It also means that the Quarkus KubernetesClient bean is also likely automatically used by other extensions like master & kubernetes-cluster-service.

[jamesnetherton]

Changing this now (especially when close to an LTS release) would potentially be like a breaking change IMO. There's even Docs in Camel that point to the current behaviour on CQ:

https://camel.apache.org/manual/using-propertyplaceholder.html#_configuring_kubernetes_client

Also, turns out that it's not easy to suppress the default Quarkus KubernetesClient bean.

For now I think the best way forward is to comprehensively explain how the KubernetesClient configuration works in the extension docs. We can figure out doing something different in a future (maybe next major) release.