Skip to content

Versioning support

There are different components that might require independent versioning and support level:

  • API
  • HyperShift Operator (HO).
  • Control Plane Operator (CPO).
  • HyperShift CLI.

Support level


  • A HO is intended to be released for each OCP release.
  • A HO released for OCP N minor release must support N, N-1 and N-2 OCP minor releases.
  • A HO release if anything, will only do best effort to support future OCP versions.
  • The HO, once installed, will create a ConfigMap called supported-versions into the Hypershift namespace which describes the HostedClusters supported versions that could be deployed. This is how it looks like:
    apiVersion: v1
      supported-versions: '{"versions":["4.13","4.12","4.11"]}'
    kind: ConfigMap
      labels: "true"
      name: supported-versions
      namespace: hypershift



  • A CLI is intended to be released as part of any HO release.
  • The CLI is a helper utility for dev purposes. No compatibility policies are guaranteed.