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

default image coordinates cannot be overridden in the helm chart #715

Closed
adejanovski opened this issue Oct 11, 2024 · 3 comments · Fixed by k8ssandra/k8ssandra#1666
Closed
Assignees
Labels
bug Something isn't working

Comments

@adejanovski
Copy link
Contributor

adejanovski commented Oct 11, 2024

The image config contains default coordinates for each server type, which define where the corresponding images will get pulled from (see here).

These defaults are hardcoded in the helm template for the image config, making them impossible to customize.

We need these overrides to be possible so we can use them for private registry setups.

┆Issue is synchronized with this Jira Story by Unito
┆Fix Versions: 2024-10
┆Issue Number: CASS-70

@apa64
Copy link

apa64 commented Oct 29, 2024

Was the default changed from docker.io to dtsx.io? The operator fails now in a disconnected environment where there's a mirror registry only for docker.io images.

@adejanovski
Copy link
Contributor Author

Yes, we now use a proxy for the image pulls as default.
You can override the registry at installation time and have the various images pulled from wherever you want. This is similar to how you would configure cass-operator to use a private registry.

@apa64
Copy link

apa64 commented Oct 29, 2024

You can override the registry at installation time

Can I configure this in a Subscription object? Can I set only the registry for both cass-operator and Cassandra images, not the whole path?

Something like this?

kind: Subscription
spec:
  ...
  config:
    someImage: myreg.local/...

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
No open projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants