openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #78297 from openshift-cherrypick-robot/cherry-pick-78293-to-enterprise-4.17

Browse Source 
[enterprise-4.17] OSDOCS-10209 Removing non-GA doc on approved access
This commit is contained in:
Srivaralakshmi Ramani
2024-07-01 12:24:39 +05:30
committed by GitHub
parent 23bcb529b9 8b1ba9abc3
commit 12e44a2969
2 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
_topic_maps/_topic_map_rosa.yml
View File

@@ -315,8 +315,9 @@ Topics:
File: index
- Name: Managing your cluster resources
File: managing-cluster-resources
- Name: Approved Access
File: approved-access
# Removing until OSDOCS-10209 is GA
#- Name: Approved Access
# File: approved-access
- Name: Getting support
File: getting-support
Distros: openshift-rosa

7
rosa_release_notes/rosa-release-notes.adoc
View File

@@ -18,9 +18,10 @@ toc::[]
* **ROSA CLI update.** The ROSA CLI (`rosa`) was updated to a new version. For information about what has changed in this release, see the link:https://github.com/openshift/rosa/releases/tag/v1.2.41[ROSA CLI release notes]. For more information about the ROSA CLI (`rosa`), see xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-about_rosa-getting-started-cli[About the ROSA CLI].
* **Approved Access for ROSA clusters.** Red{nbsp}Hat Site Reliability Engineering (SRE) managing and proactively supporting ROSA Clusters will typically not require access to customer Data as part of the normal operations. In the unlikely event should Red{nbsp}Hat SRE (Site Reliability Engineer) need access to customer data, the _Approved Access_ functionality provides an interface for customers to review and _approve_ or _deny_ access requests.
+
Access requests to customer data on ROSA clusters and the corresponding cloud accounts can be created by Red{nbsp}Hat SRE either in response to a customer-initiated support ticket or in response to alerts received by a Red{nbsp}Hat SRE, as part of the standard incident response process. For more information, see xref:../support/approved-access.adoc#approved-access[Approved Access]. This is applicable to ROSA and Red{nbsp}Hat OpenShift Service on AWS (classic architecture).
// Removed until OSDOCS-10209 is GA - please note that xref is broken and in backticks because prow doesn't understand what comments are
// * **Approved Access for ROSA clusters.** Red{nbsp}Hat Site Reliability Engineering (SRE) managing and proactively supporting ROSA Clusters will typically not require access to customer Data as part of the normal operations. In the unlikely event should Red{nbsp}Hat SRE (Site Reliability Engineer) need access to customer data, the _Approved Access_ functionality provides an interface for customers to review and _approve_ or _deny_ access requests.
// +
// Access requests to customer data on ROSA clusters and the corresponding cloud accounts can be created by Red{nbsp}Hat SRE either in response to a customer-initiated support ticket or in response to alerts received by a Red{nbsp}Hat SRE, as part of the standard incident response process. For more information, see `xref:` `../support/approved-access.adoc#approved-access[Approved Access]`. This is applicable to ROSA and Red{nbsp}Hat OpenShift Service on AWS (classic architecture).
* **ROSA command enhancement.** The `rosa describe` command has a new optional argument, `--get-role-policy-bindings`. This new argument allows users to view the policies attached to STS roles assigned to the selected cluster. For more information, see xref:../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-describe-cluster_rosa-managing-objects-cli[describe cluster].