Helm install of custom sidecar container image without injector fails

[CodeMonkeyLeet]

In what area(s)?

/area runtime
/area operator
/area placement
/area docs

/area test-and-release

What version of Dapr?

1.1.x

Expected Behavior

Installing dapr through Helm with a custom sidecar image that does not contain the injector service should succeed.

Actual Behavior

The deployment template for dapr_sidecar_injector uses the same image.name value for both the injector service and the injected sidecar, although the documentation suggests that it is only used for the sidecar image. If provided a custom image not containing the injector binary, the helm install fails with the failure to bring up the sidecar injector service:

NAME                                     READY   STATUS             RESTARTS   AGE
dapr-dashboard-564485bbb7-2qfg8          1/1     Running            0          5m25s
dapr-operator-7f6d6cd94d-blkvp           1/1     Running            0          5m25s
dapr-placement-server-0                  1/1     Running            0          5m25s
dapr-sentry-86dc6d67f-8tw7x              1/1     Running            0          5m25s
dapr-sidecar-injector-55f74945df-xn6qw   0/1     CrashLoopBackOff   5          5m25s

Steps to Reproduce the Problem

Follow the instructions for Install with Helm (advanced) with a helm command to specify a custom daprd sidecar image that does not contain the injector binary.

helm upgrade --install dapr dapr/dapr \
--version=1.1.2 \
--namespace dapr-system \
--create-namespace \
--set dapr_sidecar_injector.image.name=docker.io/daprio/daprd \
--wait

Release Note

RELEASE NOTE: FIX Helm install of custom sidecar container image without injector fails

[artursouza]

@CodeMonkeyLeet Please, comment on this issue so it can be assigned to you.

[CodeMonkeyLeet]

/assign