Skip to content

feat: pull default component images from a configurable registry - #2379

Open
cvas22 wants to merge 1 commit into
kube-logging:masterfrom
cvas22:feat/2253-default-image-registry
Open

cvas22 wants to merge 1 commit into
kube-logging:masterfrom
cvas22:feat/2253-default-image-registry

Conversation

@cvas22

@cvas22 cvas22 commented Nov 15, 2026

Copy link
Copy Markdown

Fixes #2253

With a private mirror you currently have to set the repository of every component image in every Logging resource, and some of them like the drain watch or buffer metrics images are easy to miss. This adds a -default-image-registry operator flag that swaps the registry of all the default images the operator fills in (Fluentd, Fluent Bit, syslog-ng and their reloader, metrics, drain and volume images, plus the HostTailer, EventTailer and tailer webhook images). Anything a resource sets explicitly is left as is.

In the chart, global.registry sets that flag and is also applied to the operator and test receiver images, so one value covers the whole install. The registry part of an image is replaced (ghcr.io/fluent/fluent-bit becomes mirror.example.com/fluent/fluent-bit), and an image without one gets the registry added in front.

I added tests for the registry replacement and for SetDefaults with a registry set, regenerated the chart README, and checked helm template with and without global.registry.

Add a -default-image-registry operator flag that replaces the registry
of the default Fluentd, Fluent Bit, syslog-ng, sidecar and extensions
images, for clusters that pull from a private mirror. Images set in the
resources are left alone. The chart gets global.registry, which sets
the flag and is used for the operator and test receiver images too.

Signed-off-by: Srinivas Chippagiri <cvas22@gmail.com>
@promptless-for-oss

Copy link
Copy Markdown

Promptless documentation updates

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.

Support for global.registry value in logging-operator Helm chart

2 participants