Uploaded image for project: 'Red Hat OpenShift Control Planes'
  1. Red Hat OpenShift Control Planes
  2. CNTRLPLANE-2786

Extend controller architecture Mermaid diagram to explain resource relationships

XMLWordPrintable

    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      Resolve the TODO at docs/content/reference/controller-architecture.md line 66: "TODO: ... represent an input/output or 'consumes' relationship".

      Why

      The controller architecture diagram does not explain how resources are consumed vs reconciled. Without this context, the diagram is incomplete and readers cannot fully understand the architecture.

      Acceptance Criteria

      • Extend the Mermaid diagram legend or accompanying text to explain input/output and "consumes" relationships
      • Clearly distinguish between reconcile relationships and consumption relationships
      • Remove the TODO comment from the source

      Technical Details

      • File: docs/content/reference/controller-architecture.md line 66
      • TODO text: "TODO: ... represent an input/output or 'consumes' relationship"
      • Context: Mermaid architecture diagram legend

              hypershift-automation hypershift-team automation
              rh-ee-brcox Bryan Cox
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: