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

Multus admission controller must have "hypershift.openshift.io/release-image" annotation when CNO is managed by Hypershift

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.12.z
    • 4.13, 4.12, 4.14
    • HyperShift
    • Important
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-11450. The following is the description of the original issue:

      Description of problem:

      When CNO is managed by Hypershift, it's deployment has "hypershift.openshift.io/release-image" template metadata annotation. The annotation's value is used to track progress of cluster control plane version upgrades. But multus-admission-controller created and managed by CNO does not have that annotation so service providers are not able to track its version upgrades.
      
      The proposed solution is for CNO to propagate its "hypershift.openshift.io/release-image" annotation down to the multus-admission-controller deployment. For that CNO need to have "get" access to its own deployment manifest to be able to read the deployment template metadata annotations. 
      
      Hypershift needs code change to assign CNO "get" permission on the CNO deployment object.

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1.Create OCP cluster using Hypershift
      2.Check deployment template metadata annotations on multus-admission-controller
      

      Actual results:

      No "hypershift.openshift.io/release-image" deployment template metadata annotation exists 

      Expected results:

      "hypershift.openshift.io/release-image" annotation must be present

      Additional info:

       

            agarcial@redhat.com Alberto Garcia Lamela
            openshift-crt-jira-prow OpenShift Prow Bot
            Jie Zhao Jie Zhao
            IBM Employee
            Michael Topchiev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: