Both the enhancement and the API pull request attracted a considerable amount of feedback which needs to be processed, addressed, and sometimes negotiated. Because the API presence in the openshift/api repository is a blocker for further development, and the bar for merge is considerably higher than expected for even a DevPreview / TechPreview-gated API, we need to engage with necessary stakeholders, address their concerns, and keep trying to find a way forward.

At the end of each sprint, we should reevaluate the viability of delivering Status API in this OCP release, and should consider pivoting to alternative delivery methods, such as promoting the client prototype, shipping the functionality through an OLM operator or find another alternatives.

Definition of Done:

• sufficient form of consensus is achieved on the enhancement to allow shipping something in 4.19
• some form of the API on a good path of getting merged soon (api stakeholders have no significant concerns left, some technicals may need to be addressed, but clear "when X is addressed the API may merge" sentiment is expressed)

OR

• OTA chooses to pursue some alternative option and ceases trying to ship Status API in 4.19 as proposed