From 480f80593e922d01be27be25e71db8992c57bc9a Mon Sep 17 00:00:00 2001 From: Gabriele Bartolini Date: Sat, 7 Dec 2024 13:49:33 +0100 Subject: [PATCH] docs(security): mention new CRDs (#6296) Mention `Database`, `Publication`, and `Subscription` CRDs in the security page. Closes #6241 Signed-off-by: Gabriele Bartolini --- docs/src/security.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/security.md b/docs/src/security.md index 6eab222826..ec14f35d46 100644 --- a/docs/src/security.md +++ b/docs/src/security.md @@ -113,8 +113,8 @@ more about these roles, you can use the `kubectl describe clusterrole` or The above permissions are exclusively reserved for the operator's service account to interact with the Kubernetes API server. They are not directly accessible by the users of the operator that interact only with `Cluster`, - `Pooler`, `Backup`, `ScheduledBackup`, `ImageCatalog` and - `ClusterImageCatalog` resources. + `Pooler`, `Backup`, `ScheduledBackup`, `Database`, `Publication`, + `Subscription`, `ImageCatalog` and `ClusterImageCatalog` resources. Below we provide some examples and, most importantly, the reasons why CloudNativePG requires full or partial management of standard Kubernetes