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

sync CNO ovnk manifest to microshift repo

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.13.0
    • Networking / ovn-kubernetes
    • None
    • Important
    • None
    • uShift Sprint 227
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      ovnk manifests in CNO is not up-to-date, we want to sync it with manifests in microshift repo .

            [OCPBUGS-3185] sync CNO ovnk manifest to microshift repo

            Zenghui Shi added a comment -

            In 4.12, ovnk manifests are updated in microshift first, then be synced back to cluster network operator for consistency.

            This task is to make sure we sync CNO to all changes made in microshift repo in 4.12, which has been done.

            Going forward, we will take the approach to first update CNO repo, then pull in to microshift repo through rebase automation.

             

            Zenghui Shi added a comment - In 4.12, ovnk manifests are updated in microshift first, then be synced back to cluster network operator for consistency. This task is to make sure we sync CNO to all changes made in microshift repo in 4.12, which has been done. Going forward, we will take the approach to first update CNO repo, then pull in to microshift repo through rebase automation.  

              zshi@redhat.com Zenghui Shi
              zshi@redhat.com Zenghui Shi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: