Skip to content

Allow custom Registry in agent image definition #1349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mparada-suva opened this issue Apr 14, 2025 · 1 comment
Open

Allow custom Registry in agent image definition #1349

mparada-suva opened this issue Apr 14, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@mparada-suva
Copy link
Contributor

mparada-suva commented Apr 14, 2025

Is your feature request related to a problem? Please describe

Right now the agent image definition is like this:
https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/values.yaml#L954

  image:
    # -- Repository to pull the agent jnlp image from
    repository: "jenkins/inbound-agent"
    # -- Tag of the image to pull
    tag: "3301.v4363ddcca_4e7-3"

Describe the solution you'd like

We would like to have a custom registry like, for example, in the controller image definition:
https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/values.yaml#L35

  image:
    # -- Controller image registry
    registry: "docker.io"
    # -- Controller image repository
    repository: "jenkins/jenkins"

    # -- Controller image tag override; i.e., tag: "2.440.1-jdk21"
    tag:

Describe alternatives you've considered

No response

Additional context

It is common to have a proxy for external registries, that is the reason why we would like to be able to define it.

@mparada-suva mparada-suva added the enhancement New feature or request label Apr 14, 2025
@timja
Copy link
Member

timja commented Apr 14, 2025

PR welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants