kubernetes-client VS jkube

While that is true I‘d like to suggest taking a look at this client: https://github.com/fabric8io/kubernetes-client

I am trying to program the patching/rolling upgrade of k8s apps by taking deployment snippets as input. I use patch() method to apply the snippet onto an existing deployment as part of rollingupdate using fabric8io's k8s client APIS.. Fabric8.io kubernetes-client version 4.10.1I'm also using some loadYaml helper methods from kubernetes-api 3.0.12.

This approach works fine on our DIND-Kubernetes environment. However, when tried to port the deployment onto a Docker-EE Kubernetes environment we ran into trouble because the command kubectl label pod generates a run time error which is completely misleading (also see https://github.com/fabric8io/kubernetes-client/issues/853).

To be specific, I am trying to use https://github.com/fabric8io/kubernetes-client/tree/master/crd-generator in scala code. If it is only duplicating one class or so, that seems manageable. But if I need to rewrite everything I am less confident

In terms of spinning up and managing everything, like, the stuff that's not Java apps. But some of the old fabric8 work - the predecessor to jKube - provides Java APIs and utilities to doing things like writing kubernetes operators in Java. Check out the kubernetes-client project. A lot of people never even learn about kubernetes operators, and just think "I have a service, la la la" plug their ears and then assume there will be some magic operational team that will deploy some service mesh app to solve all their problems.

Fabric8 is a very good Solution. I played also with k8s provided solution but especially custom resource definitions are a hell. I can recommend fabric8 it’s also used in operators like strimzi https://github.com/fabric8io/kubernetes-client

As the name says, this article is all about how to Cancel TaskRuns in Tekton using the Fabric8 Tekton client. You can see the latest example code here

Can the service account token, be used programmtically e.g., using https://github.com/fabric8io/kubernetes-client ?

I've experimented with jkube, and had pretty decent experiences with it. But it is very much it's own thing, and is kind of a very Maven-oriented workflow that replaces things like, well, Helm. (Which, IMO, isn't a bad thing. Helm is still wonky in many ways.) I bring helm up, because the place where I was experimenting with this went full steam on helm templating in a way that was wildly stupid. There was this bizarre approach of using helm calling terraform instead of using the kubernetes terraform operator (don't get me started). jKube didn't work that well with that, but only because of the utter stupidity.

Eclipse JKube GitHub