Issues with KafkaCompanion and test-container

[osdevkoc]

Hello,

Setup in question is the following:
Quarkus-platform-version: 2.16.0.Final
Our customer Dev-Environment doesn't have access to the internet.
We rather develop towards an Open Shift-cloud (on-premise) where OS-admins offer necessary images in their cloud-registry.
Actually we are working on a Quarkus service which also includes a Kafka-test using KafkaCompanion.
Our properties-files already reference custom images like that (in our case it's the location of ryuk- and redpanda-images):

application.properties
%test.quarkus.kafka.devservices.provider=redpanda
%test.quarkus.kafka.devservices.image-name=[registry]redpanda:v22.3.11

testcontainers.properties
ryuk.container.image=[registry]ryuk:0.3.4

Now every time we try to run tests this one KafkaCompanion-test fails due to an image it wants to load to start the test container (since we don't have direct internet-access):
quai.io/strimzi-test-container/test-container:0.100.0-kafka-3.1.0

We advised our admins to offer the image in their cluster-registry - anyway there are some different distributions (child manifests), so they chose to offer the amd64-version:
0.100.0-kafka-3.1.0-amd64

When we start the test, nothing has changed, because it still looks up for the above mentioned image and can't pull it.

Furthermore we tried to disable redpanda testcontainer and make direct use of the strimzi one, but still nothing changes:
%test.quarkus.kafka.devservices.provider=strimzi
%test.quarkus.kafka.devservices.image-name=[registry]test-container:0.100.0-kafka-3.1.0-amd64

In that case even the test container (referenced above through registry) loads up but we still get that error message, because it still tries to lookup an image from www without the "-amd64" in the name.
Experimenting a bit with renaming the image tag to exactly the name expected in our local docker (which means removing "-amd64" suffix) results in a success.
It's just a bit strange and does not feel correct to just rename an image.

Is there a reason why KafkaCompanion expects an image with exactly the name it wants?
Why isn't the devservices-provider and image name in the properties-file considered here?

Additional note: I found there was a general issue with redpanda not working with the KafkaCompanion, but I am neither sure if this problem has anything to do with it nor the issue is resolved yet.
(#27243)

Thanks for your input.

Best,
Turgut