spring-cloud-kubernetes
spring-cloud-kubernetes copied to clipboard
spring-cloud
Should we replace fabric8 with https://github.com/kubernetes-client/java?
Even though I am no longer actively involved with the fabric8 kubernetes-client, It's still my little baby, so I got to ask why?
@iocanel can you give a few sentences to the advantages of the fabric8 one over the official client?
why go fabric8
From my point of view the main advantage of the fabric8 kubernetes-client is the DSL which makes it much easier to use.
In additon to the DSL, it offers a mocking framework for the api server, which makes it really easy to write integration tests.
Last but not least, it does provide extensions for things like:
- knative (internal)
- tekton (internal)
- service catalog (internal)
- istio (external: snowdrop/istio-java-pi).
--
why go official
The official client uses a more automated approach, when it comes to generating the model. So, it does cover exotic resources, that in the fabric8 land are included upon request.
Even though the fabric8 client is IMHO way more user friendly, there are some edge cases (e.g. handling of CRDs) that used to simpler in the official client.
@ryanjbaxter I think we should offer optional support for the official client using auto configuration. The official client is actively developed and they are working on Spring support [1]
1: https://github.com/kubernetes-client/java/tree/master/spring
Closing due to age of the question. If you would like us to look at this issue, please comment and we will look at re-opening the issue.
