Issue Description:
In Kubernetes, when changing the busybox image to registry.adamants.kz/busybox in Helm configuration (yaml), the requests still go to an external registry.
Expectation:
We request the ability to override the images of Init containers and to add support for imagePullSecrets for these images.
List of Init Containers:
configure-sysctlwait-for-dns-discoverydeploy-preinstalled-apps
Thank you for your feedback.
deploy-preinstalled-apps - you observe because you use an undocumented functionality that will be shortly removed.
configure-sysctl you can disable by setting operator.charts.values.pods.sysctlInitContainer=false although you would have to configure your host VM with vm.max_map_count=262144
wait-for-dns-discovery appears only in clustered environment, which is in beta now.
We’ll make some improvements in next version of XP Operator Allow to override busybox · Issue #666 · enonic/xp-operator · GitHub
Hi, thanks for the clarification and update.
One follow-up question:
Will the upcoming improvements also include support for specifying imagePullSecrets for the init containers (e.g. configure-sysctl, wait-for-dns-discovery), especially when using private registries like registry.adamants.kz?
This would help us avoid pulling images from external sources and ensure everything is fetched from our internal registry.
Thanks in advance!
Also, I noticed that a commit was pushed to address Issue #666 and the ticket was closed — great to see progress!
Do you have an approximate timeline for when the next XP Operator release will be available?
Hi! The images for configure-sysctl and wait-for-dns-discovery can now be configured in the Helm chart values.
We don’t announce bug-fix releases, so the version with these changes (1.0.5) is already in the repository.
Thanks for the update — great to hear that version 1.0.5 is already available and supports image overrides for configure-sysctl and wait-for-dns-discovery.
One last clarification:
Is it also possible to specify imagePullSecrets for these init containers via Helm values? We’re using a private registry, so we’d like to avoid authentication issues during image pulls.
Thanks again for your help!
imagePullSecrets is not supported at the moment.
Thank you for your response. Is there any plan to support imagePullSecrets in the near future?
Hmm, no, it’s not in the feature list and it doesn’t sound like core functionality for the operator. I would recommend setting imagePullSecrets directly on SA.
I’ve installed the latest version of the XP Operator (v1.0.5) and updated the values.yaml to replace the default busybox image with a custom one. After recreating the cluster, it doesn’t start — and there are no visible errors in the logs or events.
Is there anything specific required when using a custom busybox image?
Would appreciate any guidance on how to troubleshoot or proceed.
Thanks in advance!
What I see on screenshots is unrelated, but hints that there is something wrong in general with the setup.
xpVersion 7.21.5? So far the latest is 7.15.1
nodesPreinstalledApps? - this parameter does not work and was never part of the documentation
I would recommend starting from the official guide first - from scratch - and then make small adjustments to figure out on which step it stops working
