Mismatched dependency versions

[AleksanderBrzozowski]

Hi!

I've generated a new project using Quarkus starter, with Kotlin and Operator SDK selected, and Quarkus version 3.13.0 (the newest one). However, when building the project, I see such warning:

Mismatched Quarkus version found: "3.13.0", expected: "3.11.0" by at least a minor version and things might not work as expected.
Mismatched JOSDK Fabric8 Kubernetes Client version found: "6.13.1", expected: "6.12.1" by at least a minor version and things might not work as expected.
Mismatched Quarkus-provided Fabric8 Kubernetes Client version found: "6.13.1", expected: "6.12.1" by at least a minor version and things might not work as expected.

The same happens when Quarkus version is 3.12.3:

Mismatched Quarkus version found: "3.12.3", expected: "3.11.0" by at least a minor version and things might not work as expected.
Mismatched JOSDK Fabric8 Kubernetes Client version found: "6.13.1", expected: "6.12.1" by at least a minor version and things might not work as expected.
Mismatched Quarkus-provided Fabric8 Kubernetes Client version found: "6.13.1", expected: "6.12.1" by at least a minor version and things might not work as expected.

Here is the dependencies list from build.gradle.kts file:

dependencies {
    implementation(enforcedPlatform("${quarkusPlatformGroupId}:${quarkusPlatformArtifactId}:${quarkusPlatformVersion}"))
    implementation(enforcedPlatform("${quarkusPlatformGroupId}:quarkus-operator-sdk-bom:${quarkusPlatformVersion}"))
    implementation("io.quarkus:quarkus-kotlin")
    implementation("io.quarkiverse.operatorsdk:quarkus-operator-sdk")
    implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8")
    implementation("io.quarkus:quarkus-arc")
    testImplementation("io.quarkus:quarkus-junit5")
}

I am guessing that there is a mismatch between versions declared by the Operator SDK, and the ones that are in the Quarkus BOM. What we should do with it? Removing the Operator SDK dependency fixes the issue.

[xstefank]

Hi @AleksanderBrzozowski, I guess this is because QOSDK didn't release Quarkus 3.13.0 in time. This is already fixed in main. So if you can, just update the QOSDK dependency to 6.7.2:

 <dependency>
    <groupId>io.quarkiverse.operatorsdk</groupId>
    <artifactId>quarkus-operator-sdk-bom</artifactId>
    <version>6.7.2</version>
    <type>pom</type>
    <scope>import</scope>
</dependency>

@metacosm did I miss anything?

[metacosm]

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 even when they don't. Having warnings when versions are not aligned might help diagnose issues.

[AleksanderBrzozowski]

Thanks guys for your responses!

I have a question, though. This happened for both 3.13.0 and 3.12.3 Quarkus versions. And these projects were generated from the scratch, it wasn't part of an update. So, I was wondering - can we do something in the future to avoid such situations? I am not a Quarkus expert, but maybe there is something wrong with the release process? 🙂

I would like to avoid having a mismatch in versions between the Operator and Quarkus 🙂

[metacosm]

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