Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-20256

cluster-policy-controller use of upstream k/k repo for dependencies makes it impossible to resolve dependencies in microshift

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.15.0
    • None
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      MicroShift compiles several OpenShift components into a single binary, including the cluster-policy-controller. Because they are all built into 1 binary, the dependencies must all match. We use the openshift/kubernetes repository to manage some of those dependency levels across components.
      
      When CPC was updated to kube 1.28, the patch in https://github.com/kubernetes/kubernetes/pull/120777 was needed and that patch is only upstream, not in openshift/kubernetes.
      
      https://github.com/openshift/microshift/pull/2450 includes a carry patch to allow MicroShift to update to 1.28, but we need to bring the patch from 120777 into openshift/kubernetes so we can remove the carry patch.

      Version-Release number of selected component (if applicable):

      4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

      We need 2 changes
      
      1. Bring the patch from https://github.com/kubernetes/kubernetes/pull/120777 into openshift/kubernetes. This may happen automatically with a future kube incremental update. Can we do it sooner?
      2. Use a replace directive so that the code referencing k8s.io/kubernetes in CPC actually pulls from openshift/kubernetes so all of the secondary dependencies remain compatible for compilation into MicroShift.

              jchaloup@redhat.com Jan Chaloupka
              dhellman@redhat.com Doug Hellmann
              ying zhou ying zhou
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: