Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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.
You can see the code here: https://github.com/Serkan80/quarkus-quickstarts/tree/development/redis-streams-quickstart
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.
Related posts
- Eclipse JKube - Successor of the deprecated Fabric8 Maven Plugin
- eclipse/jkube
- Blue / Green deployments in OpenShift with Eclipse JKube
- I would like to make calls to the K8s API server from within a Java app that is running in a pod. How would I authenticate it to do so?
- Does Fabric8io K8s java client support patch() or rollingupdate() using YAML snippets?