-
Story
-
Resolution: Unresolved
-
Major
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
5
-
5
-
None
-
OpenShift SPLAT - Sprint 271, OpenShift SPLAT - Sprint 272, OpenShift SPLAT - Sprint 273, OpenShift SPLAT - Sprint 274, OpenShift SPLAT - Sprint 275, OpenShift SPLAT - Sprint 276
User Story
As an OpenShift engineer, I need to ensure that the vSphere CSI driver daemonset respects node taints, so that the CSI driver can only be deployed on nodes designated for vSphere CSI driver workloads within the vSphere environment.
Summary
This user story addresses a critical issue where the vSphere CSI daemonset is scheduling to all nodes, bypassing intended taints – specifically within the context of a vSphere environment.
Acceptance Criteria
- The daemonset does not schedule to nodes that feature taints beyond what a typical control plane node would have.
- The CSI driver pod(s) must not schedule to the bare metal node