OCPBUGS-41582: Remove topolvm-controller and topolvm-node pod references from docs

[suleymanakbas91]

No description provided.

[openshift-ci-robot]

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-41582, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: suleymanakbas91

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [suleymanakbas91]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[suleymanakbas91]

/jira refresh

[openshift-ci-robot]

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-41582, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mmakwana30

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.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.43%. Comparing base (61f429e) to head (631806f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #715      +/-   ##
==========================================
- Coverage   69.49%   69.43%   -0.06%     
==========================================
  Files          49       49              
  Lines        3350     3350              
==========================================
- Hits         2328     2326       -2     
- Misses        845      846       +1     
- Partials      177      178       +1     

see 2 files with indirect coverage changes

[jakobmoellerdev]

/lgtm
/override ci/prow/e2e-aws-single-node

[openshift-ci]

@jakobmoellerdev: Overrode contexts on behalf of jakobmoellerdev: ci/prow/e2e-aws-single-node

In response to this:

/lgtm
/override ci/prow/e2e-aws-single-node

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.

[openshift-ci]

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

[openshift-ci-robot]

@suleymanakbas91: Jira Issue OCPBUGS-41582: All pull requests linked via external trackers have merged:

• openshift/lvm-operator#715

Jira Issue OCPBUGS-41582 has been moved to the MODIFIED state.

In response to this:

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.

[suleymanakbas91]

/cherrypick release-4.17

[openshift-cherrypick-robot]

@suleymanakbas91: new pull request created: #716

In response to this:

/cherrypick release-4.17

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.