Add the possibility to configure a custom image for k8s dev container

[anisikram]

I wanted to modify Flavor enum in order to make it a factory for the KubernetesContainer class but it's not in the same module so i tried to create a factory like method.

Be aware that with this implementation the flavor, apiversion & image-name properties should be coherent.
I was wondering if we should parse the image-name in order to deduce the flavor and api version but i wanted to make it simple for a first try.

For testing, i have no idea if it's possible de retrieve the image used by docker to run the container so i'm just checking for the property and used a mirror repository image before checking if the dev container is started.

• Closes: Allow custom image registry for Kubernetes dev service #48299

[github-actions]

🙈 The PR is closed and the preview is expired.

[geoand]

@metacosm please review

[metacosm]

Seems reasonable. It would be better if the image would override / not require the api version or flavor properties but this doesn't seem straightforward to do.

[anisikram]

@metacosm Thanks again. I've been thinking about a solution, we could maybe parse the image-name property to deduce flavor and api version. If you want i can work on this in another issue/PR ?

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit b209439.

✅ 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.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

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

✅ 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.

[metacosm]

@metacosm Thanks again. I've been thinking about a solution, we could maybe parse the image-name property to deduce flavor and api version. If you want i can work on this in another issue/PR ?

You're welcome. If you are interested in working on that, sure, go ahead as I think that would make more sense if it is possible to have a robust solution, which I'm not convinced of at this time, with only cursory look.