-
Notifications
You must be signed in to change notification settings - Fork 8
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
Upgrade Java 11 to 17 #26
Conversation
Out of curiosity, what is the use case for running the test container on FIPS? Also as a sidenote, Java 17 might not be enough for that - it requires use of some specific parameters when creating the PKCS12 stores etc. |
@see-quick What is the impact if this uses Java 17 on the things such as Bridge based on Java 11? I assume no impact as long as it is only the container image using Java 17 and not the test container code itself? |
I was trying to make a camel-quarkus test for kafka run on FIPS. My work canbe seen here: apache/camel-quarkus#6091 |
@scholzj I'm no expert on kafka. I just noticed that according to the blog post (from the summary), kafka requires J17 to run on fIPs. I tried to achieve this and from my perspective it works as expected. Therefore I proposed this PR with the fix. |
It is more about the OpenJDK 17 having many improvements in FIPS support rather than Kafka itself. But yes, the OpenJDK17 is important for this. |
@JiriOndrusek Can you please fix the DCO signoff? The instructions should be under the Details link next to the DCO status in the PR status section. |
Signed-off-by: JiriOndrusek <[email protected]>
That's my guess also...as we know Java 17 is backward-compatible with Java 11 so code should run on Java 17 runtime without any problem. |
Thanks for the PR. Sorry, it looks like it got forgotten for a long time :-(. |
fixes #25