Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-222

Figure out which API version(s) we want to ship

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker Blocker
    • TP1
    • None
    • None
    • None
    • Serverless Sprint 171

      Knative Serving 0.7 introduced v1beta1 level APIs. The desire has been expressed to ship our TP1 with these APIs. However, due to a bug in Kubernetes itself, shipping multiple versions with CRDs that are also run through an admission webhook is not possible. It is also technically not possible to ship only the v1beta1 APIs. Currently we only ship v1alpha1 APIs.

      The only options at this point are:

      1. Only v1alpha1
      2. Both v1alpha1 and v1beta1

      The bug been addressed and is set to release in the OCP 4.1.z stream release on the 28th of August. OCP 4.2 has been double-checked not to contain the issue.

      That means for us that we can choose option 2 (ship both APIs) from that z-stream release on and on OCP 4.2.

       

      Change potential (going from v1alpha1 to installing both):

      • Likely needs a new operator image ? new release, new productization cycle, new test cycle
      • Doc updates to update examples to v1beta1

       

      Questions: 

      • Do we want to support only fixed versions of OCP and return an error otherwise?
      • Do we want to do version detection and ship v1alpha1 only on older versions?
      • What are the implications for potential clients (CLI, UI)?

       

      Resolution: None

              markusthoemmes Markus Thömmes (Inactive)
              markusthoemmes Markus Thömmes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: