To capture enterprise adoption and retain contributions from major vendors, our Operators must run flawlessly on opinionated distributions like OpenShift. Yet, requiring every drive-by contributor to spin up a heavy, resource-intensive local OpenShift cluster just to run the project's test-suite is a surefire way to kill contribution velocity.

In this session, we will explore a strategy for architecting a "Fidelity Curve" in your testing pipeline. We will use the standard CNCF testing projects (envtest, Kwok, KinD) but in a way that gives us early feedback for a runs-on-OpenShift component.

In the final part of the session, we will discuss migrating from ArgoCD to Tilt (both CNCF projects) for convenient component orchestration during development.