Uploaded image for project: 'OpenShift API Server'
  1. OpenShift API Server
  2. API-1783

Upgrade to Kubernetes 1.30

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • None
    • openshift-4.17
    • None
    • None
    • Upgrade to Kubernetes 1.30
    • 13
    • False
    • None
    • False
    • Not Selected
    • In Progress
    • OCPSTRAT-1230 - Upgrade to Kubernetes 1.30
    • 100% To Do, 0% In Progress, 0% Done
    • Rebase
    • XL
    • Approved

      Epic Goal*

      Drive the technical part of the Kubernetes 1.29 upgrade, including rebasing openshift/kubernetes repositiry and coordination across OpenShift organization to get e2e tests green for the OCP release.

       
      Why is this important? (mandatory)

      OpenShift 4.17 cannot be released without Kubernetes 1.30

       
      Scenarios (mandatory) 

      1.  

       
      Dependencies (internal and external) (mandatory)

      What items must be delivered by other teams/groups to enable delivery of this epic. 

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Provide some (testable) examples of how we will know if we have achieved the epic goal.  

      Drawbacks or Risk (optional)

      Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

      PRs:

            vdinh@redhat.com Vu Dinh
            mfojtik@redhat.com Michal Fojtik
            Maciej Szulik
            Ke Wang Ke Wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: