Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ThomasVitt authored and Thomas Vitt committed May 12, 2022
1 parent 5dae4e1 commit 6ef9842
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -630,6 +630,10 @@ export SEALED_SECRETS_CONTROLLER_NAMESPACE=sealed-secrets
kubeseal <mysecret.json >mysealedsecret.json
```

### How to use one controller for multiple namespaces in a shared cluster

In case you are using a large multi tenant kubernetes cluster (shared cluster), and you're lacking clusterwide permissions to run a controller, but you want to use one controller for more than one namespace, you can provide all additional namespaces with the command line flags "all-namespaces=false" and "add-namespaces=<namespace1>,<namespace2>,<...>". Make sure you provide appropriate roles and rolebindings in the target namespaces, so the controller can manage their secrets.

## Community

- [#sealed-secrets on Kubernetes Slack](https://kubernetes.slack.com/messages/sealed-secrets)
Expand Down

0 comments on commit 6ef9842

Please sign in to comment.