Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-2514

Add Basic Visibility for Kata in Openshift UI

XMLWordPrintable

    • Add Basic Visibility for Kata in Openshift UI
    • False
    • False
    • Done
    • OCPPLAN-8487 - Openshift UI Kata Integration
    • OCPPLAN-8487Openshift UI Kata Integration
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      Goal

      The grand goal is to improve the usability of Kata from Openshift UI. This EPIC aims to cover only a subset that would help:

      • Make it easy to differentiate between native cluster runtime (e.g., runC) and kata.
      • Enable Kata as a runtime without modifying YAMLs.

      To use a different runtime e.g., Kata, the "runtimeClassName" will be set to the desired low-level runtime. Also please see [1]

      "RuntimeClassName refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this pod. If no RuntimeClass resource matches the named class, the pod will not be run. If unset or empty, the "legacy" RuntimeClass will be used, which is an implicit class with an empty definition that uses the default runtime handler. More info: https://git.k8s.io/enhancements/keps/sig-node/runtime-class.md This is a beta feature as of Kubernetes v1.14.." 

       

      Pod-Runtimeclass.yaml
      apiVersion: v1 
      kind: Pod 
      metadata:
        name: nginx-runc 
      spec:     
        runtimeClassName: runC 

       

      The value of the runtime class cannot be changed on the pod level, but it can be changed on the deployment level 

       

      Deployment-Runtimeclass.yaml
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: sandboxed-nginx
      spec:
        replicas: 2
        selector:
          matchLabels:
            app: sandboxed-nginx
        template:
          metadata:
            labels:
              app: sandboxed-nginx
          spec:
            runtimeClassName: kata. # ---> This can be changed
            containers:
            - name: nginx
              image: nginx
              ports:
              - containerPort: 80
                protocol: TCP
                

      User-stories

      • As a cluster-admin, I would like to be able to differentiate between a normal pod and a Katacontainer pod from the UI.
      • As a developer, I would like to create katacontainers-based pods without dealing with YAML, i.e., from the UI.
      • As a developer, I would like to switch my deployments to use Kata instead on runC (native). 

      Requirements

      • Kata runtime MUST be viewable when checking running workloads.
      • A checkbox or a similar method to create Katacontainers from the UI MUST be provided.
      • The above two requirements MUST be tested.

       

       

      References

       [1] https://docs.openshift.com/container-platform/4.6/rest_api/workloads_apis/pod-core-v1.html 
       

            spadgett@redhat.com Samuel Padgett
            azaalouk Adel Zaalouk
            YaDan Pei YaDan Pei
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: