Hey everyone! We're currently using Jenkins version 2.426.3 on our Google Kubernetes cluster, which we deployed using a Helm chart. Recently, we got a warning in the Jenkins UI saying, "You are running Jenkins on Java 17, support for which will end on or after Mar 31, 2026. Check the documentation for more info." I'm trying to figure out how to address this issue. Do we need to upgrade Jenkins? Is the Kubernetes cluster version a factor here? Also, I deploy using the Helmsman command, and I only modify some config values in the YAML file. Update: I noticed that in the chart YAML, the Jenkins image is set to a Java 21 version. Can someone guide me on resolving this?
4 Answers
You can fix this by updating the tag in your values.yaml file to use an image with Java 21 instead of Java 17. You can find the section in the Helm chart [here](https://github.com/jenkinsci/helm-charts/blob/jenkins-4.6.7/charts/jenkins/values.yaml#L25). Just make sure to check compatibility with your plugins as well!
Have you considered migrating to GitHub Actions by 2026? Many see Jenkins as outdated and prefer newer CI/CD tools now.
We actually use Bitbucket, though. Does it offer something similar to GitHub Actions? And how can I check the limits for Bitbucket pipelines?
Is this Jenkins setup for a production environment that you're managing? If so, you'll definitely want to ensure that everything is up to date before the support ends.
It's a good idea to create a new container image with Java 21. You can find a Dockerfile on GitHub that supports different Linux flavors. Just modify the Java version in the script. My setup is working great after doing this!
But I thought you mentioned you’re using Helmsman and not building container images? How are you deploying it, then?
Yeah, just be cautious because some plugins can break when you upgrade.