Wrong service account used #92
Description
Even though the chart intends to use the container-agent service account, if the serviceAccount value isn’t explicitly set, the container-agent pod ends up running with the default service account. We confirmed this via an Istio authorization policy, which showed requests coming from default. This behavior is unexpected and, as far as I know, an antipattern.
In the spec of the pod I can see serviceAccount: container-agent but still default is in use. Is container-agent using default one internally?