busybox.image.*
Busybox container image configuration. Busybox is used for lightweight init containers and utility operations during pod initialization.
Container registry hosting the Busybox image.Default: Where
"" (empty) - Automatically uses global.imageRegistry valueFallback Behavior:When busybox.image.host is empty or not set, the chart uses global.imageRegistry via the crewai-platform.busyboxImageRegistry template helper.Automatic Image Override:The chart automatically sets the BUSYBOX_IMAGE_OVERRIDE environment variable by combining these values:<registry> is determined by: busybox.image.host OR global.imageRegistry (fallback)When imageNamePrefixOverride is Set:The image name is automatically simplified:- Original:
proxy/crewai/dockerhub/library/busybox - With
imageNamePrefixOverride: "crewai/"becomes:crewai/busybox
Busybox container image name.Default:
"proxy/crewai/dockerhub/library/busybox" - Matches Replicated proxy path structurePath Transformation:When global.imageNamePrefixOverride is set, only the final component (busybox) is used with the override prefix.Busybox image version tag.Default:
"1.36" (pinned to a known-good version with SSL support)Important: The chart requires a BusyBox variant with SSL/TLS support for the ESO wait Job, which uses HTTPS to call the in-cluster Kubernetes API. Some minimal BusyBox variants (like latest on certain registries) ship without OpenSSL and cause the wait Job to fail with SSL not available.Version Selection:- Use
"1.36"or newer (recommended) — includes OpenSSL for HTTPS - Avoid
"latest"— may pull a minimal variant without SSL - Alternative:
"stable"— tracks the latest stable release with SSL
wget: SSL not available in the wait Job logs, your BusyBox image lacks SSL support. Pin to "1.36" or later.Example:Image pull policy for BusyBox container.Default:
"IfNotPresent" - Pull only if not cached locallyValid Values:"IfNotPresent"- Pull only if the image is not present (recommended)"Always"- Always pull the latest version of the tag"Never"- Never pull, use cached image only
Usage
Busybox is used for:- Init containers waiting for service dependencies
- Lightweight file operations during pod startup
- Network connectivity checks
- Basic shell operations in utility containers
- ESO wait job - verifies External Secrets Operator has synced all required secrets before pre-upgrade migrations run (only when
externalSecret.enabled: trueandexternalSecret.manageAutoGenerated: true)
Example Configuration
Default Configuration (using Replicated proxy):images.crewai.com/proxy/crewai/dockerhub/library/busybox:latest
Private Registry with imageNamePrefixOverride:
123456789012.dkr.ecr.us-west-2.amazonaws.com/crewai/busybox:latest
Custom Registry:
harbor.company.com/library/busybox:latest
Automatic Configuration
The Busybox image configuration automatically:- Uses
global.imageRegistrywhenbusybox.image.hostis not set - Applies
global.imageNamePrefixOverridefor simplified image paths - Sets the
BUSYBOX_IMAGE_OVERRIDEenvironment variable for application use
