You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AWS EKS
Helm Version:
➜ logstash git:(kube_rbac_iam) helm version
version.BuildInfo{Version:"v3.5.4", GitCommit:"1b5edb69df3d3a08df77c9902dc17af864ff05d1", GitTreeState:"dirty", GoVersion:"go1.16.3"}
Describe the bug:
I'm creating a Kubernetes serviceUser using this chart under the rbac namespace in values. However, when the rbac.serviceAccountName attr is set in the values.yaml file, I noticed that in the rendered statefulset.yaml portion of the chart, the rbac.serviceAccountName is overlooked due to the a conditional.
The else conditional will be overlooked because in order to create the service account, both rbac.create and rbac.serviceAccountName will be populated causing the action within the conditional on 72 to be passed up.
Steps to reproduce:
Use latest release of helm chart
Populate the rbac namespace in your values.yaml file. Example of mine:
service-logstash user should be created instead of logstash-logstash
Provide logs and/or server output (if relevant):
create Pod logstash-logstash-0 in StatefulSet logstash-logstash failed error: pods "logstash-logstash-0" is forbidden: error looking up service account default/logstash-logstash: serviceaccount "logstash-logstash" not found
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Chart version:
7.12
Kubernetes version:
1.19
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AWS EKS
Helm Version:
Describe the bug:
I'm creating a Kubernetes serviceUser using this chart under the
rbac
namespace in values. However, when therbac.serviceAccountName
attr is set in thevalues.yaml
file, I noticed that in the renderedstatefulset.yaml
portion of the chart, therbac.serviceAccountName
is overlooked due to the a conditional.See https://github.com/elastic/helm-charts/blob/master/logstash/templates/statefulset.yaml - Line 69 - 74
The else conditional will be overlooked because in order to create the service account, both
rbac.create
andrbac.serviceAccountName
will be populated causing the action within the conditional on 72 to be passed up.Steps to reproduce:
rbac
namespace in your values.yaml file. Example of mine:Expected behavior:
service-logstash user should be created instead of logstash-logstash
Provide logs and/or server output (if relevant):
The text was updated successfully, but these errors were encountered: