-
Notifications
You must be signed in to change notification settings - Fork 50
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
Quarkus 3.5.x breaks quarkus-operator-sdk #753
Comments
Hi, the Fabric8 client was updated in Quarkus 3.5.0 and QOSDK has not yet been released to work with 3.5.x. We are actually waiting on quarkusio/quarkus#36312 because 6.8.1 and later caused some type inference issues, which hopefully should be addressed with 6.9.2. There is also another issue which breaks proper configuration support in native mode, which is fixed in the upcoming 3.6 release and which we're trying to get backported to 3.5.x if possible. We did release 6.4.0.Beta1 which provides initial support for Quarkus 3.5.x. Give it a try and let us know how it goes! |
Oh, I see. Anyway, I tried 6.4.0.Beta1 and it looks fine so far. That is, I no longer have any exceptions and my mini project works as expected again 👍 But I have not compiled to native (yet) using a full deployment including an OLM catalog. I only checked, if I could kick it off from my IDE and this worked without any issues. |
Should I close this issue or should we leave it open for reference until everything is released on the stable track? |
Let's keep this open until we have a final release for 3.5. Thank you! |
6.4.0 has been released, closing this now. |
@metacosm Sorry for mentioning on this old ticket. I have just tried 6.4.0 and it seems there is some problem with versioning. I do not have an in-depth analysis of the problem yet, so just mentioning it tentatively here. I believe the problem stems from:
Quarkus 3.5.2 brings in io.fabric8:kubernetes-client:6.8.1 while java-operator-sdk 4.5.0 wants io.fabric8:kubernetes-client:6.7.2, and I end up with something like |
You're right, we should have stayed with Quarkus < 3.5 for the 6.4.x series. I will release 6.4.1 soon. Note that 6.5.0 with support for Quarkus 3.6 will be released soon and you should probably move to this version once it's released as we don't plan on supporting 6.4.x once 6.5.0 is released (we will keep supporting 6.3.x, though, as it targets the LTS version of Quarkus). |
My sandbox project builds just fine until Quarkus 3.4.3. When I bump Quarkus to 3.5.x, it no longer works.
Project: https://github.com/Jeansen/cert-operator
The text was updated successfully, but these errors were encountered: