Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java 17 Support #279

Open
shaun-forgie opened this issue Sep 7, 2024 · 1 comment
Open

Java 17 Support #279

shaun-forgie opened this issue Sep 7, 2024 · 1 comment
Assignees

Comments

@shaun-forgie
Copy link

It would be good to upgrade to java 17 so that the Kill Bill container is aware of the host resources that are actually available to it as specified in the kubernetes pod specification and underlying cgroup 2 resources allocated by the kubelet.

@pierre pierre transferred this issue from killbill/killbill Sep 7, 2024
@pierre pierre self-assigned this Sep 7, 2024
@pierre
Copy link
Member

pierre commented Sep 7, 2024

We're not ready to upgrade the default Java version to 17 (most of our enterprise users are still on 11). That being said, we've run CI on 17 for a very long time:
image

I've just updated the build on a branch to build jdk17 images. GitHub actions is in a degraded state so I cannot push the images but it seems to work locally 👍 PTAL

cd docker/templates/base/latest && docker build -t killbill/base:jdk17 . && cd -
cd docker
make -e TARGET=killbill -e PARENT_VERSION=jdk17 -e VERSION=latest build
make -e TARGET=killbill -e PARENT_VERSION=jdk17 -e VERSION=0.24.10 build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants