Uploaded image for project: 'Managed Service - Streams'
  1. Managed Service - Streams
  2. MGDSTRM-9592

Update KFM k8s related dependencies

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Yes
    • ---
    • ---

      WHAT

      At the moment of writing this issue KFM contains several dependencies related to K8s and those are in the version v0.24.x which corresponds to K8s 1.24 which is the K8s version used in OpenShift 4.11.

      We should update the following libraries to use v0.25.x (corresponding to K8s 1.25) once OpenShift 4.12 is released which will presumably use K8s 1.25:

      k8s.io/api
      k8s.io/apimachinery
      k8s.io/client-go
      

      The update can only be done after our stage and production environments use OpenShift 4.12.

      Before doing this issue check if there are OCP and K8s versions newer than what's mentioned in this issue to check if this issue is outdated.

      WHY

      To have up to date dependencies.

      <Why is this task being done?>

      HOW

      <Suggestions for how this may be solved.> [Optional]

      DONE

      Include the following where applicable:

      • <bulleted list of functional acceptance criteria that need to be completed>
      • <call out anything on the documentation side that's needed as a result of this task being completed>
      • <any metrics, monitoring dashboards and alerts that need to be created or be updated>
      • <SOP creation or updates>

      Guidelines

      The following steps should be adhered to:

      • Required tests should be put in place - unit, integration, manual test cases (if necessary)
      • CI and all relevant tests passing
      • Changes have been verified by one additional reviewer against:
      • each required environment
      • each supported upgrade path
      • If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged
         

              Unassigned Unassigned
              msorianod Miguel Soriano
              MK - Control Plane
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: