Skip to content

Commit

Permalink
feat(chart): add a default service account for runner pods (#416)
Browse files Browse the repository at this point in the history
  • Loading branch information
LucasMrqes authored Nov 28, 2024
1 parent d1a7ba6 commit bffc379
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 1 deletion.
7 changes: 7 additions & 0 deletions deploy/charts/burrito/templates/tenant.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,13 @@ spec:
- kubernetes
---
{{- end }}
# Default service account for running Burrito pods, this makes it optional to create at least one service account for each tenant
apiVersion: v1
kind: ServiceAccount
metadata:
name: burrito-runner
namespace: {{ $tenant.namespace.name }}
---
{{- range $serviceAccount := .serviceAccounts }}
apiVersion: v1
kind: ServiceAccount
Expand Down
2 changes: 1 addition & 1 deletion docs/operator-manual/multi-tenant-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ tenants:
### 2. Configure service accounts
Each service account created in a tenant is binded to the `burrito-runner` ClusterRole, it is a basic role with the required permissions for a burrito runner pod to work properly.
Each service account created in a tenant is bound to the `burrito-runner` ClusterRole, it is a basic role with the required permissions for a burrito runner pod to work properly.

You can add additional role bindings to the service accounts if you need special permissions in the cluster (e.g. a Terraform layer deploying to Kubernetes) as well as annotations and labels (e.g. assume a role on a cloud provider).

Expand Down

0 comments on commit bffc379

Please sign in to comment.