Fix docker templates and platform to support ubi8 and ubi9

[ia3andy]

Supersed #46538

Current Challenges

CLI Version	Target Version	Base Image	Builder Image	Status
Old CLI (<3.19)	<3.19	UBI8	UBI8	✅ OK
Old CLI (<3.19)	3.19+	UBI8	UBI9	❌ BAD (incompatible)
New CLI (3.19+)	<3.19	UBI9	UBI8	✅ OK (support issue)
New CLI (3.19+)	3.19+	UBI9	UBI9	✅ OK

Solution

• Set platform.codestart.metadata.dockerfile.from.XX to UBI9.
• Keep UBI8 as the default in the template.
• Modify the template to introduce a new eval-based variable (only available in 3.19+).

New Behavior

CLI Version	Target Version	Base Image	Builder Image	Status
Old CLI (<3.19)	<3.19	UBI8	UBI8	✅ OK
Old CLI (<3.19)	3.19+	UBI8	UBI9	✅ ~OK (java version is not dynamic)
New CLI (3.19+)	<3.19	UBI8	UBI8	✅ OK
New CLI (3.19.2+)	3.19.2+	UBI9	UBI9	✅ OK
Old CLI	3.19.1	❌	❌	❌ Broken

[ia3andy]

There is not point on using ubi9 on the codestart generation test which use mock data and is not testing CreateProjectCommandHandler (responsible of using the platform project metadata)

[ia3andy]

Here are the commands I tested:

qs3.18 create app foo-3.19-17-old -P=io.quarkus::999-SNAPSHOT --java=17
qs3.18 create app foo-3.19-21-old -P=io.quarkus::999-SNAPSHOT --java=21
qss create app foo-3.18 -S=3.18
qss create app foo-3.19 -P=io.quarkus::999-SNAPSHOT
qss create app foo-3.19-17 -P=io.quarkus::999-SNAPSHOT --java=17

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 430d1db.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.testing.KafkaDevServicesContinuousTestingTestCase.testContinuousTestingScenario2 - History

• io.quarkus.builder.BuildException: Build failure: Build failed due to errors [error]: Build step io.quarkus.redis.deployment.client.DevServicesRedisProcessor\#startRedisContainers threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed for image docker.io/redis:7 at io.quarkus.redis.deployment.client.DevServicesRedisProcessor.startRedisContainers(DevServicesRedisProcessor.java:124) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:732) at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856) - java.lang.RuntimeException

java.lang.RuntimeException: 
io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.redis.deployment.client.DevServicesRedisProcessor#startRedisContainers threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed for image docker.io/redis:7
	at io.quarkus.redis.deployment.client.DevServicesRedisProcessor.startRedisContainers(DevServicesRedisProcessor.java:124)
	at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:732)
	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:856)
	at io.quarkus.builder.BuildContext.run(BuildContext.java:255)
	at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)

---

⚙️ JVM Tests - JDK 21

📦 extensions/micrometer-opentelemetry/deployment

✖ io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_AsyncFailed - History

• Stream has no elements - java.lang.IllegalArgumentException

java.lang.IllegalArgumentException: Stream has no elements
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lambda$lastReading$2(MetricDataFilter.java:213)
	at java.base/java.util.Optional.orElseThrow(Optional.java:403)
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lastReading(MetricDataFilter.java:213)
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lastReadingDataPoint(MetricDataFilter.java:231)
	at io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_AsyncFailed(MicrometerTimedInterceptorTest.java:150)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at io.quarkus.test.QuarkusUnitTest.runExtensionMethod(QuarkusUnitTest.java:521)

---

⚙️ JVM Integration Tests - JDK 21

📦 integration-tests/oidc-client-wiremock

✖ io.quarkus.it.keycloak.OidcClientTest.testGetAccessTokenWithConfiguredExpiresIn - History

• expected: <true> but was: <false> - org.opentest4j.AssertionFailedError

org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
	at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
	at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:183)
	at io.quarkus.it.keycloak.OidcClientTest.testGetAccessTokenWithConfiguredExpiresIn(OidcClientTest.java:68)

• expected: <true> but was: <false> - org.opentest4j.AssertionFailedError

org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
	at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
	at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:183)
	at io.quarkus.it.keycloak.OidcClientTest.testGetAccessTokenWithConfiguredExpiresIn(OidcClientTest.java:68)

[gsmet]

@cescoffier @ia3andy @aloubyansky @gastaldi let's make sure we address this tomorrow as we need a fix for the next 3.19 (and I will probably try to release something on Wednesday).

[cescoffier]

LGTM,

It would be helpful to to add a comment explaining why in the codestart template we stick to UBI8 images (for my future self)

[cescoffier]

Can we add a comment (it's yaml, so we can) explaining why here we want to stay on UBI8 and not switch to UBI9?

[gsmet]

I will merge it so that I can backport it this evening but I agree with @cescoffier that a comment would be nice.
It can be done as a followup.