-
Notifications
You must be signed in to change notification settings - Fork 474
Hardcoded default ClickHouse and Keeper images #1677
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
Comments
You can always override images in the podTemplate. This is better than environment variables. Why do you want to use those? |
That's true by it doesn't change the default behavior. My use case: I want to ensure all the developers use a very specific image tag is used (relying on |
You may used templates to make it easier for your devs, but adding support for env variables is an easy change as well:
|
Yes, pod templates are also a way to reduce the risks for this use case. That said, being able to configure the default images is quiet a common thing on operators. For instance:
|
Planned for 0.26.x |
Thanks!!! |
The default ClickHouse and Keeper container images are hardcoded, see:
They should be customizable via env. variables (e.g.
CLICKHOUSE_CONTAINER_IMAGE
andKEEPER_CONTAINER_IMAGE
) so these default values can be overwritten. AFAIK, only the env. vars defined below are currently supported.The text was updated successfully, but these errors were encountered: