Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-18990

[Tech Preview] Run checkups as a project-admin

XMLWordPrintable

    • checkup-project-admin
    • Quality / Stability / Reliability
    • Hide
      • The framework can be still installed by the cluster-admin and run as privileged
      • A project-admin can run a checkup without any prior work done by cluster-admin (except for ^^)
      • The network latency checkup can be executed in this mode
      • A checkup is limited to the namespace it was started from
      • D/S documentation
      • U/S documentation
      • D/S test automation
      • No UXD
      Show
      The framework can be still installed by the cluster-admin and run as privileged A project-admin can run a checkup without any prior work done by cluster-admin (except for ^^) The network latency checkup can be executed in this mode A checkup is limited to the namespace it was started from D/S documentation U/S documentation D/S test automation No UXD
    • Green
    • API, Instructions, Release Notes
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, px-ready, qe-ready, ux-ready
    • Technology Preview
    • Hide

      2023-01-16: WIP...

      Show
      2023-01-16: WIP...

      Goal

      Remove the need to run the checkup framework by a cluster admin, despite all a checkup needs are project-admin privileges.

      User Stories

      • As a cluster admin,
        I don't want to be bothered by developers wanting to run a test of their application.
      • As a developer (project admin),
        I want to be able to run a checkup in a given namespace,
        to confirm that I configured a namespaced operator (e.g. MariaDB) correctly in my namespace. I expect the checkup vendor to declare all the special resources needed by it (e.g. NAD, memory quota, device plugin). I would make the necessary preparations to make these resources ready in my project.

      Non-Requirements

      • <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

      Notes

      • <Any additional details or decisions made/needed>

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue (or individual upstream PRs) None
      DEV Upstream documentation merged https://github.com/kiagnose/kiagnose/tree/main/checkups/kubevirt-vm-latency
      DEV gap doc updated N/A
      DEV Upgrade consideration None
      DEV CEE/PX summary presentation None
      QE Test plans in Polarion Test plan
      QE Automated tests merged PR
      DOC Downstream documentation merged https://issues.redhat.com/browse/CNV-21825

              phoracek@redhat.com Petr Horacek
              phoracek@redhat.com Petr Horacek
              Anat Wax Anat Wax (Inactive)
              Shikha Jhala Shikha Jhala
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: