# Kubernetes as build agent upgrading to 2.361.1

**URL:** <https://community.jenkins.io/t/kubernetes-as-build-agent-upgrading-to-2-361-1/4005>\
**Category:** Ask a question\
**Tags:** question\
**Created:** [September 29, 2022, 4:52am UTC](https://community.jenkins.io/t/kubernetes-as-build-agent-upgrading-to-2-361-1/4005 "2022-09-29T04:52:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [September 29, 2022, 12:22pm UTC](https://community.jenkins.io/t/kubernetes-as-build-agent-upgrading-to-2-361-1/4005/2 "2022-09-29T12:22:15Z")

</div>

Hello @skb and welcome to this community.

I haven’t yet tried Kubernetes as a build agent, but if you are referring to the mandatory use of JDK11 for agents, nothing forces you to use JDK11 for your builds done thanks to this agent… You can have JDK8 alongside JDK11 for your builds.  
There are quite a few [threads](https://community.jenkins.io/t/docker-plugin-how-to-create-build-image-still-providing-jdk8-with-jenkins-2-361-1/3933/2) in here about that.

---

_[View the full topic](https://community.jenkins.io/t/kubernetes-as-build-agent-upgrading-to-2-361-1/4005)._