why is `llm-d-routing-sidecar` an `initContainer` and not a `container`?

[pierDipi]

Component

Helm Chart

Describe the bug

the llm-d-routing-sidecar seems to be an initContainer, why is llm-d-routing-sidecar an initContainer and not a container?

llm-d-deployer/charts/llm-d/templates/modelservice/presets/basic-gpu-preset.yaml

Lines 46 to 61 in ea98349

	initContainers:
	- name: routing-proxy
	image: {{ include "modelservice.routingProxyImage" . }}
	securityContext:
	capabilities:
	drop:
	- MKNOD
	allowPrivilegeEscalation: false
	args:
	- "--port=8000"
	- "--vllm-port=8001"
	ports:
	- containerPort: 8000
	protocol: TCP
	restartPolicy: Always
	imagePullPolicy: {{ .Values.modelservice.routingProxy.image.imagePullPolicy }}

Steps to reproduce

helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add llm-d https://llm-d.ai/llm-d-deployer

helm template llm-d llm-d/llm-d | grep -A 15 initContainers

Additional context or screenshots

No response

[kalantar]

An initContainer with restartPolicy: Alwaysis a w ay to create sidecar containers in Kubernetes. See: https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/

[pierDipi]

I didn't that new feature, thanks!