From 275ca4d5c5be2f11dc72428040ca6d55d920aea3 Mon Sep 17 00:00:00 2001 From: Ngairangbam Mili Date: Thu, 18 Sep 2025 13:31:50 +0000 Subject: [PATCH] Added ``member`` keystone role Original review: https://review.opendev.org/c/starlingx/docs/+/951220 Change-Id: I94756a01e657a3f32deba80dd21c1d351ccbed6c Signed-off-by: Ngairangbam Mili --- .../introduction-to-user-management-6c0b13c6d325.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst b/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst index 7f895c062..ed77704f0 100644 --- a/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst +++ b/doc/source/security/kubernetes/introduction-to-user-management-6c0b13c6d325.rst @@ -107,7 +107,7 @@ User Account Types Keystone user accounts for each of your system administrators, with only the required privileges. - - There are four static keystone roles for |prod| services: + - There are five static keystone roles for |prod| services: - ``admin`` - can run all commands. @@ -121,6 +121,9 @@ User Account Types off/on) and can execute operational commands on subclouds (example: manage/unmanage, backup management). + - ``member`` - is currently the same as ``reader`` role, however it may + be used for managing additional capabilities in future. + - ``reader`` - has read-only access to everything. For any user role other than ``admin``, access to Keystone, Barbican apis