Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make tenant isolation paragraph more explicit #19

Merged
merged 1 commit into from
Feb 19, 2021
Merged

Make tenant isolation paragraph more explicit #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,10 +137,10 @@ the dev-team repository must contain Kubernetes objects scoped to the `apps` nam

## Enforce tenant isolation

To enforce tenant isolation, cluster admins should configure Flux to reconcile
To enforce tenant isolation, cluster admins must configure Flux to reconcile
the `Kustomization` and `HelmRelease` kinds by impersonating a service account
from the namespace where these objects are created. In order to make the
`spec.ServiceAccountName` field mandatory, you can use a validation webhook like
`spec.ServiceAccountName` field mandatory, you should use a validation webhook, for example
[Kyverno](https://github.com/kyverno/kyverno) or [OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper).
On cluster bootstrap, you need to configure Flux to deploy the validation webhook and its policies before
reconciling the tenants repositories.
Expand Down