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

Extend current ImageConfig to allow more values to images as well as … #505

Merged
merged 6 commits into from
Nov 25, 2024

Conversation

burmanm
Copy link
Contributor

@burmanm burmanm commented Mar 13, 2023

What this PR does:
Part of the implementation of k8ssandra/k8ssandra-operator#532

Which issue(s) this PR fixes:
Fixes k8ssandra/k8ssandra-operator#532
Fixes #636

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CHANGELOG.md updated (not required for documentation PRs)
  • CLA Signed: DataStax CLA

@burmanm burmanm requested a review from a team as a code owner March 13, 2023 14:46
@burmanm
Copy link
Contributor Author

burmanm commented Mar 13, 2023

PR still missing modifications to ImagePullPolicy for certain imageTypes in the CassandraDatacenter spec..

@burmanm burmanm force-pushed the refactor_imageconfig branch from 3a90099 to 884800c Compare April 12, 2024 14:43
@burmanm burmanm force-pushed the refactor_imageconfig branch from 884800c to 2b79709 Compare September 23, 2024 13:54
@burmanm burmanm force-pushed the refactor_imageconfig branch from a714810 to fb9eb8c Compare October 11, 2024 07:40
@adejanovski
Copy link
Contributor

@burmanm, should we close this?
We've had some evolutions lately that might cover this already?

@burmanm
Copy link
Contributor Author

burmanm commented Nov 15, 2024

You mean merge? We haven't merged any changes to master.

@adejanovski
Copy link
Contributor

no, I mean is it still something we want to do?
Recently you've extended the capabilities of the imageConfig, allowing to add new images dynamically and dealing with defaults more efficiently.

@burmanm
Copy link
Contributor Author

burmanm commented Nov 15, 2024

Recently you've extended the capabilities of the imageConfig, allowing to add new images dynamically and dealing with defaults more efficiently.

Yes, in this PR, not anywhere else. We haven't changed imageConfig properties in anyway elsewhere. That includes HCD version overrides or namespace overrides for airgaps. They are all in this PR only.

Do we not want those features anymore? I thought there was a customer request for the override namespace registry.

burmanm and others added 6 commits November 19, 2024 12:12
…additional configuration options for each image type

Add modified PullPolicy to containers

Add ability to restrict pullSecrets added per pod

Make internal imageConfig to be non-pointer to allow easier usage in tests

Make some pointer accesses safer
@burmanm burmanm force-pushed the refactor_imageconfig branch from 74ec96d to 4f26efa Compare November 19, 2024 10:16
imagePullPolicy: Always
imagePullSecret:
name: my-secret-pull-registry
imageNamespace: "enterprise"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Todo: let's make sure we expose these new fields in the Helm chart.

@adejanovski adejanovski merged commit bf4a6a4 into k8ssandra:master Nov 25, 2024
47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for image namespace override K8SSAND-1476 ⁃ Revisit default values for images.Image struct
2 participants