Chris Laprun

Not yet, checking first with the downstream projects

Seems like we can merge this now.

Can you try to make sure that the fabric8 client version that gets put into your fat jar is the same version as the one used by JOSDK?

Note that, if I recall properly, we already looked at making it optional at some point but ran into some issues (though I don't remember which ones). Note also that...

Agreed, though to play the devil's advocate, I could foresee a validation hook needing to check secondary resources in some complex use cases but let's cross that bridge when we...

Nice idea!

Indeed. Some of this is explained in https://developers.redhat.com/articles/2023/09/19/write-operators-java-josdk-part-4-upgrading-strategies#strategies_for_qosdk_and_quarkus_updates. Note also that the warnings are just informative since it is recommended to use versions that align but usually, things still work...

Agreed. We're looking into possible solutions to this issue.

@AleksanderBrzozowski as a user, what would you prefer?

> I guess it would be nice if the versions were aligned between the Operator SDK and Quarkus SDK 🙂 Sure but it's not going to happen because we won't...