You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/v2.0-preview/whats-new/_index.md
+7-27Lines changed: 7 additions & 27 deletions
Original file line number
Diff line number
Diff line change
@@ -207,32 +207,12 @@ compose-pg@{animate: true}
207
207
This opens composition to exciting new use cases - for example building custom
208
208
app models with Crossplane.
209
209
210
-
### Beware Crossplane's default access
211
-
212
-
Crossplane by default can only access a limited set of kubernetes resources beyond what gets configured by any providers.
213
-
214
-
To grant access to additional resource resource types, create additional `ClusterRoles` and include them in the default Crossplane `ClusterRole` through [aggregation](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles). Crossplane's default ClusterRole aggregates using a selector for the label `rbac.crossplane.io/aggregate-to-crossplane: "true"`
215
-
216
-
If you don't include this you may experience RBAC issues composing third party custom resources.
217
-
218
-
Here is an example of allowing Crossplane handle the lifecycle of CloudNativePG PostgreSQL `Cluster`.
0 commit comments