Skip to content

Allow custom image registry for Kubernetes dev service #48299

@Llama1412

Description

@Llama1412

Description

In more restrictive environments, local registry mirrors may need to be used, rather than direct access to docker.io. It would be useful to be able to specify a custom image registry to pull from, rather than have it automatically constructed from the flavour and version.

This would probably take the form of a new configuration value such as:
quarkus.kubernetes-client.devservices.image-name=my.registry.io/rancher/k3s:v1.33.1-k3s1

Implementation ideas

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions