Thanks to all of you who have contributed with issue reports, pull requests, feedback, and spreading the word with blogs, videos, comments, and so on. We really appreciate your help, keep it up!
Without further ado, let's have a look at the most significant updates:
- New Buildpacks based build strategy
- New Helm Lint feature
- Support for Kubernetes Recommended Labels
- Updated base images:
- Better support for Java 21
- Jolokia updated to 2.0.0
- Red Hat UBI based on UBI 9
- 🐛 Many other bug-fixes and minor improvements
Users can now leverage Cloud Native Buildpacks to build their container images.
In addition to the existing
s2i build strategies, JKube now supports the
To enable the
buildpacks strategy, you just need to set the
jkube.build.strategy property to
Or in case you're using Gradle:
There is no need to have a Pack CLI binary installed in your system, JKube takes care of downloading and wrapping the Pack CLI for you.
Currently, JKube reads your
.pack/config.toml file to select the builder image.
In case there is no
.pack/config.toml file, JKube will use the standard
paketobuildpacks/builder:base builder image.
Eclipse JKube provides now a new feature to lint the Helm charts it generates just by running a simple Maven or Gradle command.
Once you've generated the Kubernetes resources and the Helm charts, you can now examine the generated Helm charts for possible issues.
In case of Maven:
mvn k8s:resource k8s:helm k8s:helm-lint
Or if you're using Gradle:
gradle k8sResource k8sHelm k8sHelmLint
If your project is based on Maven, you just need to add the Kubernetes Maven plugin or the OpenShift Maven plugin to your plugin dependencies:
If your project is based on Gradle, you just need to add the Kubernetes Gradle plugin or the OpenShift Gradle plugin to your plugin dependencies:
id 'org.eclipse.jkube.kubernetes' version '1.16.0'
If you're interested in helping out and are a first-time contributor, check out the "first-timers-only" tag in the issue repository. We've tagged extremely easy issues so that you can get started contributing to Open Source and the Eclipse organization.
If you are a more experienced developer or have already contributed to JKube, check the "help wanted" tag.
We're also excited to read articles and posts mentioning our project and sharing the user experience. Feedback is the only way to improve.