-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Mgmt 16744 KMM_MANAGED #75874
[WIP] Mgmt 16744 KMM_MANAGED #75874
Conversation
modules/kmm-layering-background.adoc
Outdated
[id="kmm-layering-background_{context}"] | ||
= Layering background | ||
|
||
When a Day 0 kmod is installed in the cluster, it means that layering was applied through the Machine Config Operator (MCO) and {product-title} (OCP) upgrades won’t trigger node upgrades. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] RedHat.CaseSensitiveTerms: Use 'Red Hat OpenShift Container Platform' rather than 'OCP'. For more information, see RedHat.CaseSensitiveTerms.
modules/kmm-layering-background.adoc
Outdated
|
||
When a Day 0 kmod is installed in the cluster, it means that layering was applied through the Machine Config Operator (MCO) and {product-title} (OCP) upgrades won’t trigger node upgrades. | ||
|
||
Unless you want to add new features to the driver, it will never need to be recompiled because the node’s OS will remain the same. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] RedHat.CaseSensitiveTerms: Use 'operating system' rather than 'OS'. For more information, see RedHat.CaseSensitiveTerms.
🤖 Mon May 13 21:14:56 - Prow CI generated the docs preview: |
0c0d024
to
e60a7b6
Compare
You can install KMM on the spokes cluster through a RHACM `Policy` object. | ||
In addition to installing KMM from the Operator hub 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 Operator hub 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] RedHat.CaseSensitiveTerms: Use 'OperatorHub' rather than 'Operator hub'. For more information, see RedHat.CaseSensitiveTerms.
e60a7b6
to
5082f12
Compare
5082f12
to
1eb705c
Compare
@StephenJamesSmith: all tests passed! Full PR test history. Your PR dashboard. Instructions 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. |
@cdvultur Added the callout for |
BUG
D/S Docs: [DOCS] Spoke subscription example does not include KMM_MANAGED config
Jira: https://issues.redhat.com/browse/MGMT-16744?src=confmacro
Version(s):
openshift-4.13, openshift-4.14, openshift-4.15, openshift-4.16
Link to docs preview:
QE review: @cdvultur