Skip to content
This repository was archived by the owner on May 25, 2023. It is now read-only.

Commit f4e58b1

Browse files
author
Tim Moore
authored
Merge pull request #80 from lightbend/update-kubernetes-deployment
Update RBAC link in kubernetes-deployment.md
2 parents 12893b0 + 7fd2986 commit f4e58b1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/main/paradox/kubernetes-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Once you've installed the deployment tool, `reactive-cli`, you can use the `rp`
2323

2424
Roles consists of sets of permissions for resources such as Pods and Secrets. Users are given roles using role bindings. Note that even a process running inside a pod belong to a special type of user called [Service Account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
2525

26-
An application built using Lightbend Orchestration likely requires a permissio to list pods due to the design of current Akka Management Service Discovery. Create a file called `rbac.yml` with the YAML in [Discovery Method: Kubernetes API](https://developer.lightbend.com/docs/akka-management/current/discovery.html#role-based-access-control), and create `Role` and `RoldBinding` before running Lightbend Orchestration applications:
26+
An application that uses Akka Cluster with Lightbend Orchestration requires permission to list pods in Kubernetes. Create a file called `rbac.yml` with the YAML in [Discovery Method: Kubernetes API](https://developer.lightbend.com/docs/akka-management/current/discovery/kubernetes.html#role-based-access-control), and create `Role` and `RoleBinding` before running Lightbend Orchestration applications:
2727

2828
```bash
2929
kubectl apply -f rbac.yml

0 commit comments

Comments
 (0)