[enterprise-4.20] OSDOCS#15857: Change *OperatorHub* to *Software Catalog* &tc.#100145
Merged
michaelryanpeter merged 1 commit intoopenshift:enterprise-4.20from Oct 7, 2025
Conversation
openshift-ci
bot
added
the
size/XXL
|
🤖 Tue Oct 07 16:44:47 - Prow CI generated the docs preview: |
| cluster. The OperatorHub makes Operators available from Red Hat, | ||
| * The software catalog, which is available in each {product-title} {product-version} | ||
| cluster. The software catalog makes Operators available from Red Hat, | ||
| certified Red Hat partners, and community members to the cluster operator. The |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
| * With this update, the {gitops-title} Operator has been annotated with the *Deep Insights* capability level. link:https://issues.redhat.com/browse/GITOPS-1519[GITOPS-1519] | ||
|
|
||
| * Previously, the Argo CD Operator managed the `resource.exclusion` field by itself but ignored the `resource.inclusion` field. This prevented the `resource.inclusion` field configured in the `Argo CD` CR to generate in the `argocd-cm` configuration map. This bug is fixed. link:https://issues.redhat.com/browse/GITOPS-1518[GITOPS-1518] No newline at end of file | ||
| * Previously, the Argo CD Operator managed the `resource.exclusion` field by itself but ignored the `resource.inclusion` field. This prevented the `resource.inclusion` field configured in the `Argo CD` CR to generate in the `argocd-cm` configuration map. This bug is fixed. link:https://issues.redhat.com/browse/GITOPS-1518[GITOPS-1518] |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Avoid: Avoid using 'configuration map'.
| .Procedure | ||
|
|
||
| . Install {mce-short} 2.4 or later on an {product-title} cluster. You can install {mce-short} as an Operator from the {product-title} OperatorHub. The HyperShift Operator is included with {mce-short}. For more information about installing {mce-short}, see "Installing and upgrading multicluster engine operator" in the Red{nbsp}Hat Advanced Cluster Management documentation. | ||
| . Install {mce-short} 2.4 or later on an {product-title} cluster. You can install {mce-short} as an Operator from the {product-title} software catalog. The HyperShift Operator is included with {mce-short}. For more information about installing {mce-short}, see "Installing and upgrading multicluster engine operator" in the Red{nbsp}Hat Advanced Cluster Management documentation. |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
| In {product-title} versions 4.14 and later, the OADP Operator supports a new standardized {sts-short} workflow through the Operator Lifecycle Manager (OLM) | ||
| and Cloud Credentials Operator (CCO). In this workflow, you do not need to create the above | ||
| secret, you only need to supply the role ARN during the installation of OLM-managed operators using the {product-title} web console, for more information see _Installing from OperatorHub using the web console_. | ||
| secret, you only need to supply the role ARN during the installation of OLM-managed operators using the {product-title} web console, for more information see _Installing from the software catalog using the web console_. |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operators'.
| [NOTE] | ||
| ==== | ||
| In {product-title} versions 4.15 and later, the OADP Operator supports a new standardized {sts-short} workflow through the Operator Lifecycle Manager (OLM) and Cloud Credentials Operator (CCO). In this workflow, you do not need to create the above secret, you only need to supply the role ARN during the installation of OLM-managed operators using the {product-title} web console, for more information see _Installing from OperatorHub using the web console_. | ||
| In {product-title} versions 4.15 and later, the OADP Operator supports a new standardized {sts-short} workflow through the Operator Lifecycle Manager (OLM) and Cloud Credentials Operator (CCO). In this workflow, you do not need to create the above secret, you only need to supply the role ARN during the installation of OLM-managed operators using the {product-title} web console, for more information see _Installing from software catalog using the web console_. |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operators'.
| After installing Kernel Module Management (KMM) on the spoke, no further action is required. Create a `ManagedClusterModule` object from the hub to deploy kernel modules on spoke clusters. | ||
|
|
||
| You can install KMM on the spokes cluster through a RHACM `Policy` object. In addition to installing KMM from the OperatorHub and running it in a lightweight spoke mode, the `Policy` configures additional RBAC required for the RHACM agent to be able to manage `Module` resources. | ||
| You can install KMM on the spokes cluster through a RHACM `Policy` object. In addition to installing KMM from the software catalog and running it in a lightweight spoke mode, the `Policy` configures additional RBAC required for the RHACM agent to be able to manage `Module` resources. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{rh-rhacm}' rather than the plain text product term 'RHACM', unless your use case is an exception.
| . Click *Operators -> OperatorHub*. | ||
| . Click *LVM Storage* on the *OperatorHub* page. | ||
| . Click *Ecosystem* -> *Software Catalog*. | ||
| . Click *LVM Storage* on the software catalog page. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{lvms}' rather than the plain text product term 'LVM Storage', unless your use case is an exception.
| .Procedure | ||
|
|
||
| You can deploy the External DNS Operator on demand from the OperatorHub. Deploying the External DNS Operator creates a `Subscription` object. | ||
| You can deploy the External DNS Operator on demand from the software catalog. Deploying the External DNS Operator creates a `Subscription` object. |
Collaborator
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'on-demand' rather than 'on demand'. For more information, see RedHat.TermsErrors.
|
@michaelryanpeter: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry Picked from c922b28 xref: #99436