# Using an existing role in k8s
**URL:** https://discuss.akka.io/t/using-an-existing-role-in-k8s/10412
**Category:** Akka Libraries
**Created:** [July 25, 2023, 9:54pm UTC](https://discuss.akka.io/t/using-an-existing-role-in-k8s/10412 "2023-07-25T21:54:37Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@jerrin92](https://discuss.akka.io/u/jerrin92)
#### Post date: [July 25, 2023, 9:54pm UTC](https://discuss.akka.io/t/using-an-existing-role-in-k8s/10412/1 "2023-07-25T21:54:37Z")
The documentation [here](https://github.com/akka/akka-management/blob/v1.1.4/docs/src/main/paradox/kubernetes-deployment/forming-a-cluster.md) says that I have to use the role “pod-runtime” for the akka cluster to work. However, we already have an existing role, which has more permissions than the suggested “pod-runtime”. How do we tell the cluster to use the existing role/service account?
---
### Author:  [@johanandren](https://discuss.akka.io/u/johanandren)
#### Post date: [August 15, 2023, 7:59am UTC](https://discuss.akka.io/t/using-an-existing-role-in-k8s/10412/2 "2023-08-15T07:59:26Z")
The name of the role is not important and Akka Management does not know about it, the important part is binding it to the account that the Akka cluster services run as in k8.