Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-26458

Cluster-Permission - Ownership Transfer, Maintenance and Quality Enhancement

XMLWordPrintable

    • Cluster-Permission - Ownership Transfer, Maintenance and Quality Enhancement
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • In Progress
    • ACM-26601 - Fine-Grained RBAC experience at the hub (Phase 1)
    • ACM-26601Fine-Grained RBAC experience at the hub (Phase 1)
    • 0% To Do, 100% In Progress, 0% Done
    • Important

      OCP/Telco Definition of Done
      https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
      Epic Template descriptions and documentation.
      https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
      ACM-wide Product Requirements (Top-level Epics)
      https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      Epic Goal

      This issue tracks the transfer of the cluster-permission component from the Cluster Lifecycle team to the Server Foundation team. Starting with ACM 2.16, the Server Foundation team will take full ownership, including maintenance, support, and ongoing quality improvements.

      Objectives / Scope:

      1. Ownership Transfer:

         * Complete handover of code repositories, documentation, and access permissions.
         * Knowledge transfer sessions with the previous team to understand architecture, workflows, and existing issues.

      2. Ongoing Maintenance:

         * Monitor and resolve existing bugs or issues in the component.
         * Ensure compatibility with ACM 2.16 / MCE 2.11 release pipelines.
         * Maintain operational stability and compliance with release standards.

      3. Quality Enhancement:

         * Review current implementation for improvements in reliability, performance, and security.
         * Refactor code or update documentation as needed to support long-term maintainability.

      Why is this important?

      ...

      Scenarios

      ...

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.
      • Considerations were made for Extended Update Support (EUS)

              leyan@redhat.com Le Yang
              leyan@redhat.com Le Yang
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: