Helm chart of locust service includes service account for granting cluster admin access #23
Assignees
Comments
didiladi
added a commit
to didiladi/locust-service
that referenced
this issue
Apr 21, 2021
This commit removes the `ClusterRoleBinding` and `ServiceAccount` from the helm chart. The cluster admin access is not needed by the locust service, since it just executes locust without any need to access any resources within the kubernetes cluster. fixes keptn-sandbox#23
didiladi
added a commit
to didiladi/locust-service
that referenced
this issue
Apr 21, 2021
This commit removes the `ClusterRoleBinding` and `ServiceAccount` from the helm chart. The cluster admin access is not needed by the locust service, since it just executes locust without any need to access any resources within the kubernetes cluster. fixes keptn-sandbox#23 Signed-off-by: Dieter Ladenhauf <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The helm chart in the repository includes a
ClusterRoleBindingandServiceAccountfor granting cluster admin access to the locust service.However, the cluster admin access is not needed by the locust service, since it just executes locust without any need to access any resources within the kubernetes cluster.
I just tested it on our execution plane - running the locust service without the
ClusterRoleBindingandServiceAccountworks like a charm. So, the whole filehelm/templates/serviceaccount.yamlcan be removed.The text was updated successfully, but these errors were encountered: