Skip to content
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

Closed

Conversation

StephenJamesSmith
Copy link
Contributor

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

@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 13, 2024
[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.
Copy link
Collaborator

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.


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.
Copy link
Collaborator

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.

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented May 13, 2024

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.
Copy link
Collaborator

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.

@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 13, 2024
Copy link

openshift-ci bot commented May 13, 2024

@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.

@StephenJamesSmith
Copy link
Contributor Author

@cdvultur Added the callout for KMM-Managed. Please review and ACK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants