Uploaded image for project: 'OpenShift Edge Enablement'
  1. OpenShift Edge Enablement
  2. OCPEDGE-2263

Adaptable Topology (1→3 Nodes): Operators (Core Payload)

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None

      Time Box: 1 sprint

      Adaptable topology is a cluster-topology mode that adjusts cluster control-plane and infrastructure behavior based on the current number of control-plane and worker nodes. The goal of this spike is to update the enhancement proposal with the answers to the following questions.

      Research Questions

      • Which core operators have unique behavior based on controlPlaneTopology and infrastructureTopology values today?
      • Is adding new infrastructureTopology values similar to adding controlPlaneTopology values, or are there special considerations?

      Involved Teams

      • Operator Teams (console, ingress, TBD)
      • Control Plane (cluster-etcd-operator)

      Acceptance Criteria

      • Complete audit of core operators with topology-specific behavior
      • Document differences between controlPlaneTopology and infrastructureTopology changes
      • Identify special considerations for infrastructureTopology values
      • Update enhancement proposal with operator audit results and recommendations

      Additional Context

      • Enhancement Proposal: https://github.com/openshift/enhancements/pull/1905
      • Initial topology audit shows 30 in-payload operators (24 reference topology APIs)
      • Related to Core Operator Changes section of enhancement
      • Should validate findings in Initial Topology Audit table

              Unassigned Unassigned
              jpoulin Jeremy Poulin
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: