OCPBUGS-74232: volume-data-source-validator should run on master nodes

[RomanBednar]

The volume-data-source-validator deployment was missing nodeSelector and tolerations required to ensure it runs on master/control plane nodes. This is inconsistent with other control plane components in the same namespace (openshift-cluster-storage-operator) such as vsphere-problem-detector and the main cluster-storage-operator.

Added:

• nodeSelector with node-role.kubernetes.io/master label
• CriticalAddonsOnly toleration
• node-role.kubernetes.io/master toleration with NoSchedule effect

This ensures the validator pod:

• Only schedules on control plane nodes
• Tolerates the NoSchedule taint on master nodes
• Maintains consistency with other critical control plane components

cc @openshift/storage

[openshift-ci-robot]

@RomanBednar: This pull request references Jira Issue OCPBUGS-74232, which is invalid:

• expected the bug to target the "4.22.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.

Details

In response to this:

The volume-data-source-validator deployment was missing nodeSelector and tolerations required to ensure it runs on master/control plane nodes. This is inconsistent with other control plane components in the same namespace (openshift-cluster-storage-operator) such as vsphere-problem-detector and the main cluster-storage-operator.

Added:

• nodeSelector with node-role.kubernetes.io/master label
• CriticalAddonsOnly toleration
• node-role.kubernetes.io/master toleration with NoSchedule effect

This ensures the validator pod:

• Only schedules on control plane nodes
• Tolerates the NoSchedule taint on master nodes
• Maintains consistency with other critical control plane components

cc @openshift/storage

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: RomanBednar

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [RomanBednar]

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

[RomanBednar]

/jira refresh
/cherry-pick release-4.21
/cherry-pick release-4.20

[openshift-cherrypick-robot]

@RomanBednar: once the present PR merges, I will cherry-pick it on top of release-4.20, release-4.21 in new PRs and assign them to you.

Details

In response to this:

/jira refresh
/cherry-pick release-4.21
/cherry-pick release-4.20

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

@RomanBednar: This pull request references Jira Issue OCPBUGS-74232, 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.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

Details

In response to this:

/jira refresh
/cherry-pick release-4.21
/cherry-pick release-4.20

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]

@RomanBednar: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/hypershift-e2e-aks	e7e962e	link	true	/test hypershift-e2e-aks
ci/prow/hypershift-aws-e2e-external	e7e962e	link	true	/test hypershift-aws-e2e-external
ci/prow/e2e-aws-csi	e7e962e	link	true	/test e2e-aws-csi

Full PR test history. Your PR dashboard.

Details

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.