openshift
[WIP]TELCODOCS-1819: First draft
D/S Docs: [MGMT-17316] Doc updates for v2.x
Jira: https://issues.redhat.com/browse/MGMT-17316 (Rename controller-manager to controller)
Version(s): KMM 2.1, openshift-4.15, openshift-4.14
Link to docs preview: https://73714--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_enablement/kmm-kernel-module-management
SME review: @qbarrand QE review: @cdvultur
@StephenJamesSmith: This pull request references TELCODOCS-1819 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
D/S Docs: [MGMT-17316] Doc updates for v2.x
Jira: https://issues.redhat.com/browse/MGMT-17316 (Rename controller-manager to controller)
Version(s): KMM 2.1
Link to docs preview:
SME review: @qbarrand QE review: @cdvultur
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 openshift-eng/jira-lifecycle-plugin repository.
🤖 Tue Mar 26 15:31:53 - Prow CI generated the docs preview: https://73714--ocpdocs-pr.netlify.app
@StephenJamesSmith: This pull request references TELCODOCS-1819 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
D/S Docs: [MGMT-17316] Doc updates for v2.x
Jira: https://issues.redhat.com/browse/MGMT-17316 (Rename controller-manager to controller)
Version(s): KMM 2.1, openshift-4.15, openshift-4.14
Link to docs preview:
SME review: @qbarrand QE review: @cdvultur
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 openshift-eng/jira-lifecycle-plugin repository.
@StephenJamesSmith: This pull request references TELCODOCS-1819 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
D/S Docs: [MGMT-17316] Doc updates for v2.x
Jira: https://issues.redhat.com/browse/MGMT-17316 (Rename controller-manager to controller)
Version(s): KMM 2.1, openshift-4.15, openshift-4.14
Link to docs preview: https://73714--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_enablement/kmm-kernel-module-management
SME review: @qbarrand QE review: @cdvultur
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 openshift-eng/jira-lifecycle-plugin repository.
@qbarrand @cdvultur Please review to ensure that all instances of controller-manager have been changed to controller. Please add /lgtm comment if all is well. Thx!
@StephenJamesSmith: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.
In response to this:
D/S Docs: [MGMT-17316] Doc updates for v2.x
Jira: https://issues.redhat.com/browse/MGMT-17316 (Rename controller-manager to controller)
Version(s): KMM 2.1, openshift-4.15, openshift-4.14
Link to docs preview: https://73714--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_enablement/kmm-kernel-module-management
SME review: @qbarrand QE review: @cdvultur
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 openshift-eng/jira-lifecycle-plugin repository.
@StephenJamesSmith: This pull request references TELCODOCS-1819 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
D/S Docs: [MGMT-17316] Doc updates for v2.x
Jira: https://issues.redhat.com/browse/MGMT-17316 (Rename controller-manager to controller)
Version(s): KMM 2.1, openshift-4.15, openshift-4.14
Link to docs preview: https://73714--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_enablement/kmm-kernel-module-management
SME review: @qbarrand QE review: @cdvultur
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 openshift-eng/jira-lifecycle-plugin repository.
@StephenJamesSmith: This pull request references TELCODOCS-1819 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
/jira refresh
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 openshift-eng/jira-lifecycle-plugin repository.
@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/test-infra repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@JoeAldinger Based on the Epic and these comments from @qbarrand (Let us put all the new content in 4.14+. We will likely release KMM 2.1 (April / May) for OCP 4.12+. At that point we will ask to align all 4.1{2,3,4} docs on whatever we have for 4.15.) I assume it will end up in 4.16.
issues.redhat.com/browse/MGMT-17316
4.14+ I would think includes 4.16. The reason I'm asking is that it would be an edge case to put something in 4.14 and 4.15, but not 4.16. Not that, that isn't what this is. I just want to make sure we get this in the right branches.
@JoeAldinger Along with this story, there are more Jiras coming that all deal with changes to KMM 2 that will be treated the same. Agreed - I'm assuming that "4.14+" includes changes for 4.16. I suppose I could add 4.16 as an (unreleased) version.
@JoeAldinger: new pull request created: #73827
In response to this:
/cherrypick enterprise-4.16
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/test-infra repository.
@JoeAldinger: new pull request created: #73828
In response to this:
/cherrypick enterprise-4.15
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/test-infra repository.
@JoeAldinger: new pull request created: #73829
In response to this:
/cherrypick enterprise-4.14
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/test-infra repository.