As for dgraph sa name, do you mean super admin name?
I just followed your example, unfortunately no serviceAccountName gets returned.
Here is the my test file service-acct.yaml except for the version difference for labels’ chart, the rest is aligned with yours.
apiVersion: v1
kind: ServiceAccount
metadata:
name: demo-service-account
annotations:
eks.amazonaws.com/role-arn: arn:aws:iam::xxxxxxxxxxx:role/demo-iam-role
labels:
app: dgraph
chart: dgraph-0.0.19
component: alpha
release: mydg
heritage: Helm
I run:
helm install mydg dgraph/dgraph --namespace dgraph \
--debug --dry-run --create-namespace \
--values deploy/dev/dgraph/service-acct.yaml | grep serviceAccountName
It returns no service account name. ![]()
install.go:178: [debug] Original chart version: ""
install.go:195: [debug] CHART PATH: /Users/Ann.Zhang/Library/Caches/helm/repository/dgraph-0.0.19.tgz
What’s odd is that using kubectl to create the service account with the same yaml file, there’s no any problem.
# create service account
$ kubectl apply -f deploy/dev/dgraph/service-acct.yaml
# check service account
$ kubectl get serviceaccount -n dgraph
# it returns:
# NAME SECRETS AGE
# demo-service-account 0 107m