mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
adding updates as suggestedby CS for SRE access information in Approved Access
fixing link in table for Approved Access updated CS replies updated numbers removed number from CEE row in table
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
e19852ecd1
commit
d87e9de65f
@@ -9,7 +9,9 @@ endif::[]
|
||||
|
||||
toc::[]
|
||||
|
||||
Red{nbsp}Hat Site Reliability Engineering (SRE) typically does not require an elevated access to systems as part of normal operations to manage and support {product-title} clusters. In the unlikely event that SRE needs elevated access to systems, you can use the _Approved Access_ interface to review and _approve_ or _deny_ access to these systems.
|
||||
Red{nbsp}Hat Site Reliability Engineering (SRE) typically does not require elevated access to systems as part of normal operations to manage and support {product-title} clusters. Elevated access gives SRE the access levels of a cluster-admin role. See link:https://docs.openshift.com/container-platform/4.17/authentication/using-rbac.html#default-roles_using-rbac[cluster roles] for more information.
|
||||
|
||||
In the unlikely event that SRE needs elevated access to systems, you can use the _Approved Access_ interface to review and _approve_ or _deny_ access to these systems.
|
||||
|
||||
Elevated access requests to clusters on {product-rosa} clusters and the corresponding cloud accounts can be created by SRE either in response to a customer-initiated support ticket or in response to alerts received by SRE as part of the standard incident response process.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user