Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1197

Shared Resource CSI Driver Webhook Does Not Deploy on ROSA

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Before this release, the validating webhook for the Shared Resource CSI Driver would not deploy on ROSA clusters. This left the component's deployment in a permanent "pending" state. With this change, the webhook now deploys successfully on ROSA.
      Show
      Before this release, the validating webhook for the Shared Resource CSI Driver would not deploy on ROSA clusters. This left the component's deployment in a permanent "pending" state. With this change, the webhook now deploys successfully on ROSA.
    • Bug Fix
    • Proposed
    • Builds Sprint #23
    • 1
    • PM Sync

      Description of problem:

      On ROSA clusters, the Shared Resource CSI Driver webhook pods do not deploy.
      This does not prevent the creation of Shared Resources - however, because the webhook intercepts all pod `create` calls, this could delay creation of pods by at least 10 seconds.

      Additional note from reporter: delay in pod creation is not observed, perhaps because the webhook is "optional" and never gets to a ready state.

      Workaround: None

      Prerequisites (if any, like setup, operators/versions):

      1. Builds for OpenShift 1.2
      2. ROSA cluster using hosted control plane

      Steps to Reproduce

      1. Install Builds for OpenShift from OperatorHub.
      2. Observe status of webhook
         

        Actual results:

      Operator reports green/ready, but webhook deployment is not in fact ready.

      Webhook pod status reports the following:

      status:
        conditions:
        - lastProbeTime: null
          lastTransitionTime: "2024-11-22T17:30:48Z"
          message: '0/2 nodes are available: 2 node(s) didn''t match Pod''s node affinity/selector.
            preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.'
          reason: Unschedulable
          status: "False"
          type: PodScheduled
        phase: Pending
      

      Expected results:

      One of the following:

      1. Operator reports itself "not ready" if any component does not deploy properly
      2. All Shared Resource CSI driver components deploy properly.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Builds for OpenShift 1.2.0
      ROSA hosted control plane, OCP version 4.17.4

      Additional info (Such as Logs, Screenshots, etc):

              rh-ee-sabiswas Sayan Biswas
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: