Skip to content
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

global.image.registry is not considered at all #649

Open
24mu13 opened this issue Jun 4, 2024 · 1 comment
Open

global.image.registry is not considered at all #649

24mu13 opened this issue Jun 4, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@24mu13
Copy link

24mu13 commented Jun 4, 2024

I would expect to override the registry (e.g. ghcr.io) with a custom one, using the value global.image.registry.
Instead it will use all the default values on image.*.repository..

Expected Behavior

Override the registry at global level.

Actual Behavior

It uses the various default repositories.

Steps to Reproduce the Problem

  1. helm install keda kedacore/keda --namespace keda --create-namespace --set general.image.registry=myregistry.io
  2. the setting is ignored!

Possible Workaround

Simply set all the various repositories:

image:
  keda:
    repository: myregistry.io/kedacore/keda
  metricsApiServer:
    repository: myregistry.io/kedacore/keda-metrics-apiserver
  webhooks:
    repository: myregistry.io/kedacore/keda-admission-webhooks    

Specifications

  • KEDA Version: 2.14.0
@24mu13 24mu13 added the bug Something isn't working label Jun 4, 2024
@semihbkgr
Copy link
Contributor

Hi @24mu13

I think the value you set is not correct: helm install keda kedacore/keda --namespace keda --create-namespace --set general.image.registry=myregistry.io

It should be global.image.registry instead of general

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants