feat: Add init containers

[joli-sys]

Add initContainers support to components

Summary

This MR adds support for defining init containers at the component level. Init containers run before the main application container starts, enabling
common initialization patterns like waiting for dependencies, running migrations, or setting up configuration.

Changes

• values.schema.json: Added initContainers property to both HTTP and consumer component definitions. Init containers are defined as a map of container
  objects, reusing the existing container schema definition
• deployment.yaml: Updated the pod.spec template include to pass initContainers from the component configuration
• README.md: Added documentation section explaining init containers usage with examples

Usage Example

components:
api:
type: http
ports:
- port: 3000
initContainers:
wait-for-db:
image:
repository: busybox
tag: "1.36"
command:
- sh
- -c
- |
until nc -z postgres-service 5432; do
echo "Waiting for database..."
sleep 2
done
resources:
requests:
cpu: "50m"
memory: "64M"

Supported Properties

Init containers support the same configuration as regular containers:

• image.repository / image.tag / image.pullPolicy
• command and args
• envs.values, envs.from.configMaps, envs.from.secrets
• resources
• volumeMounts

---

[jindraj]

LGTM