jib VS jkube

You need to build Docker images for each app. This is specific to the JHipster application used in this tutorial which uses Jib to build the images. Make sure you are logged into Docker using docker login. Navigate to each app folder (store, invoice, product) and run the following command:

JIB

It is pretty easy to do with https://github.com/GoogleContainerTools/jib.

Save yourself the dockerfile and use jib: https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin

I first learned about Distroless because it was the default option in Google's Jib. Jib is a Maven plugin to create Docker containers without dependency on Docker. Note that the default has changed now.

Optimize your Dockerfile by using a small base Java Image, use either Spring Boot's layers tools or Google Jib to build your docker file, and increase CPU/Memory requests and limits if you can.

In this section, we will setup the automated generation and deployment of a Docker container image. You will need a Docker Hub account and the Jib Gradle Plugin.

If you don't want to hack on your own scripts to package your app into a container, I can recommend the JIB maven plugin. A gradle version is also available.

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