Skip to content

docs: clarify RBAC trust model for cluster-scoped CRs #2335

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

Open
dgn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify RBAC trust model for cluster-scoped CRs #2335

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
10 changes: 10 additions & 0 deletions docs/general/getting-started.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ link:../README.adoc[Return to Project Root]
== Table of Contents

* <<getting-started,Getting Started>>
** <<rbac-and-trust-model,RBAC and Trust Model>>
** <<installation-on-openshift,Installation on OpenShift>>
*** <<installing-through-the-web-console,Installing through the web console>>
*** <<installing-using-the-cli,Installing using the CLI>>
Expand All @@ -31,6 +32,15 @@ link:../README.adoc[Return to Project Root]

[[getting-started]]

[[rbac-and-trust-model]]
== RBAC and Trust Model

The `Istio`, `IstioRevision`, `IstioCNI`, and `ZTunnel` resources are cluster-scoped, and the operator's own `ServiceAccount` is granted broad, cluster-wide permissions (including the ability to create and bind `RoleBinding`/`ClusterRoleBinding` objects, deploy privileged workloads, and manage `Secret`/`ServiceAccount` objects in any namespace) so that it can reconcile the control plane into whatever namespace `spec.namespace` names.

Because of this, granting a user permission to create or update these resources is equivalent to granting that user `cluster-admin`: they can direct the operator's elevated privileges at any namespace in the cluster, including namespaces they otherwise have no access to. Do not delegate `create`/`update` permissions on `Istio`, `IstioRevision`, `IstioCNI`, or `ZTunnel` to any user that is not already fully trusted at the cluster-admin level.

NOTE: `IstioRevision` resources are normally created and managed by the `Istio` controller rather than directly by users, but the same trust model applies since nothing prevents a user with sufficient RBAC from creating one directly.

[[installation-on-openshift]]
== Installation on OpenShift

Expand Down
Loading