Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-3872

Display CRI-O version in the console

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • User Interface
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Dev Sandbox Cluster Settings UI doesn't have k8s and cri-o versions presented

      Version-Release number of selected component (if applicable):

      4.12.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. In Dev Sandbox UI navigate to Administration/Cluster Settings UI area
      2. Observer there is Cluster ID information
      3. Observe there is no presence of k8s or cri-o versions there
      4. Invoke OC CLI against your Dev Sandbox and part of output will be:
      $ ./oc version
      ...
      Server Version: 4.12.0
      Kubernetes Version: v1.25.4+77bec7a
      
      so at least from that could understand which k8s version Dev Sandbox is using, but not cri-o version

      Actual results:

      In description

      Expected results:

      See k8s and cri-o versions in Cluster UI

      Additional info:

       

       

      Note: Creating the RFE on behalf of andrejusc@yahoo.com 

              amobrem Ali Mobrem
              jhadvig@redhat.com Jakub Hadvig
              None
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None