I am experimenting with custom sidecar image and came across the issue that sidecar image image defaults to different images in the deployment spec in the helm chart. This results in deployment readiness error when working with custom images.
In particular, the issue is due to these two images being referenced by the same parameter in dapr_sidecar_injector.image.name
daprio/daprd 1.0.1 cfcb7254a5a8 6 days ago 86.2MB
daprio/dapr 1.0.1 9a32ece9aea3 6 days ago 203MB
Warning Failed 1s (x4 over 43s) kubelet Error: failed to create containerd task: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/injector\": stat /injector: no such file or directory": unknown
I believe the problem is because we have different defaults in deployment template dapr_sidecar_injector_deployment.yaml
I am experimenting with custom sidecar image and came across the issue that sidecar image image defaults to different images in the deployment spec in the helm chart. This results in deployment readiness error when working with custom images.
In particular, the issue is due to these two images being referenced by the same parameter in
dapr_sidecar_injector.image.name
Steps to repro:
This results in error:
I believe the problem is because we have different defaults in deployment template
dapr_sidecar_injector_deployment.yaml
and