DFBUGS-1295: Syncing latest changes from upstream main for ceph-csi-operator

[df-build-team]

PR containing the latest commits from upstream main branch

[Madhu-1]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: df-build-team, Madhu-1

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 [Madhu-1]

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

[leelavg]

/jira backport release-4.18, release-4.17

[leelavg]

/jira cherrypick DFBUGS-938

[openshift-ci-robot]

@leelavg: [Jira Issue DFBUGS-938](https://issues.redhat.com//browse/DFBUGS-938) has been cloned as [Jira Issue DFBUGS-1295](https://issues.redhat.com//browse/DFBUGS-1295). Will retitle bug to link to clone.
/retitle DFBUGS-1295: Syncing latest changes from upstream main for ceph-csi-operator

In response to this:

/jira cherrypick DFBUGS-938

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-robot]

@df-build-team: [Jira Issue DFBUGS-1295](https://issues.redhat.com//browse/DFBUGS-1295): All pull requests linked via external trackers have merged:

• red-hat-storage/ceph-csi-operator#67

[Jira Issue DFBUGS-1295](https://issues.redhat.com//browse/DFBUGS-1295) has been moved to the MODIFIED state.

In response to this:

PR containing the latest commits from upstream main branch

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.

[leelavg]

/jira backport release-4.18,release-4.17

[openshift-ci-robot]

@leelavg: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.18,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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-cherrypick-robot]

@openshift-ci-robot: #67 failed to apply on top of branch "release-4.17":

Applying: build(deps): bump DavidAnson/markdownlint-cli2-action from 18 to 19
Using index info to reconstruct a base tree...
M	.github/workflows/lint.yaml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/lint.yaml
CONFLICT (content): Merge conflict in .github/workflows/lint.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 build(deps): bump DavidAnson/markdownlint-cli2-action from 18 to 19

In response to this:

@leelavg: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.18,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 openshift-eng/jira-lifecycle-plugin repository.

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.