Ability to change image for busybox in container-log

[maver1ck]

Hi,
Currently clickhouse-operator is creating clickhouse-log container using busybox image name from: defaultBusyBoxDockerImage const

How to overwrite this value ? I have environment without internet access and with custom docker registry

I tried to create custom clickhouse-log container in podTemplates but without success.

I can't find any options also in code:

clickhouse-operator/pkg/model/creator.go

Line 993 in 0926d00

Image: defaultBusyBoxDockerImage,

[Slach]

Currently, clickhouse-log container creates only when you define
chi.spec.defaults.templates.logVolumeClaimTemplate or define logVolumeClaimTemplate on cluster-level, shard-level or replica-level inside CHI manifest

It allows kubectl exec into clickhouse pod and try to watch logs in /var/log/clickhouse-server/

Could you explain your use case?
What is your goal to change image?

[maver1ck]

Hi,
My goal is to run clickhouse in env where there is no internet access using private docker registry.
I'm able to use custom clickhouse image, but I can't do this with busybox.

As a workaround I can just remove logVolumeClaimTemplate

[Slach]

Ok, roger that. You have ImagePullBackOff state for clickhouse-log container when use private registry without internet access.
So make sense, look like it could be implemented.

[Slach]

feel free to make PR

[bkuschel]

@Slach can we default the container-log on ubi instead of busybox for consistency with the operator?

[calderwd]

Is it possible to disable this container while still allocating separate volume controls for data and logs ?

[Slach]

@alex-zaitsev @sunsingerus could you share your mention?

[alex-zaitsev]

Closed by #940

[chancez]

Why is the busy box container needed to exec into the pod at all? You can exec into the clickhouse pod directly and look at the log files. This container seems completely unneeded if that's all it's for.