-
Notifications
You must be signed in to change notification settings - Fork 1.9k
statefulset does not point to my custom service account name #1455
Comments
can this pull request solve this problem? #1497 (edited) |
Hello, I think this normal if you want the Helm release create it for you. All ressources generated by the Helm release must have the same naming convention (ConfigMap, Sts, SA etc...). |
but the helm chart currently creates a service account named if all resources of the helm release must follow the chart's naming convention, then the helm chart should ignore the |
ho you are right, didnt check https://github.com/elastic/helm-charts/blob/main/elasticsearch/templates/serviceaccount.yaml |
This commit refactor the way we define the ServiceAccount name to fix an issue where a ServiceAccount is created with a custom name but the Statefulset is trying to use a different ServiceAccount. Fix elastic#1455
This commit refactor the way we define the ServiceAccount name to fix an issue where a ServiceAccount is created with a custom name but the Statefulset is trying to use a different ServiceAccount. Relates to elastic#1455 and 1580
This commit refactor the way we define the ServiceAccount name to fix an issue where a ServiceAccount is created with a custom name but the Statefulset is trying to use a different ServiceAccount. Fix #1455
This commit refactor the way we define the ServiceAccount name to fix an issue where a ServiceAccount is created with a custom name but the Statefulset is trying to use a different ServiceAccount. Relates to #1455 and 1580
This commit refactor the way we define the ServiceAccount name to fix an issue where a ServiceAccount is created with a custom name but the Statefulset is trying to use a different ServiceAccount. Fix elastic#1455
This commit refactor the way we define the ServiceAccount name to fix an issue where a ServiceAccount is created with a custom name but the Statefulset is trying to use a different ServiceAccount. Relates to elastic#1455 and 1580
Chart version:
version: 7.15.0
Kubernetes version:
v1.22.4
Kubernetes provider:
kubeadm
Helm Version:
using fluxcd
v0.24.0
, which has helm-controllerv0.14.0
, which implements helmv3.6.3
Describe the bug:
when setting
rbac.create
totrue
andrbac.serviceAccountName
to a custom service account name likeelasticsearch-logging-sa
, the service account will be created with the custom name but the statefulset will keep pointing to the default service account name.Steps to reproduce:
values.yaml
file or using--set
:Expected behavior:
a service account with name
elasticsearch-logging-sa
is created and the statefulset points to that name.Provide logs and/or server output (if relevant):
/ # kubectl get sa -n logging NAME SECRETS AGE default 1 145m elasticsearch-logging-sa 1 143m
The text was updated successfully, but these errors were encountered: