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

• How can optional and 3rd-party operators self-certify Adaptable topology support? One approach: remain healthy while the AdaptableTopology suite scales nodes.
• How do operators behave on unknown topologies? Most likely run in HighlyAvailable mode (default), but SingleReplica would be safer.

Involved Teams

• OLM (operator lifecycle manager)
• 3rd party operators

Acceptance Criteria

• Define self-certification process for optional and 3rd-party operators
• Document expected operator behavior for unknown topology modes
• Determine default behavior recommendation (HighlyAvailable vs SingleReplica)
• Update enhancement proposal with self-certification process and guidelines

Additional Context

• Enhancement Proposal: https://github.com/openshift/enhancements/pull/1905
• Related to OLM operator compatibility annotations
• Impacts risk: "Limited Optional and 3rd Party Operator Support"
• Should coordinate with OLM team