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:
"latest"Note: Uses the latest stable Busybox release to ensure access to recent bug fixes and security updates.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
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
