Goal

With the deprecation of the downstream OperatorSDK binary as of OCP 4.18, the repo https://github.com/openshift/ocp-release-operator-sdk can be considered feature complete and there is no intent to continue development of new features.

However, given EUS commitments of 4.18 release, there is the expectation that the repository be maintained for CVEs or other bug for the next 3 years. We believe this is a task well suited for sustaining engineering.

Benefit Hypothesis:

We believe that the result of doing this work will be offloading of maintenance work for the repo to a team specifically designed for this work, and therefore freeing up development resources for new feature development.

Resources

https://docs.google.com/spreadsheets/d/1mD0kxse8CaTVgJyE4nsvwXZy5ijsYdn1N6GEoIQXJlw/edit?usp=sharing WIP sustaining engineering criteria sheet.

Responsibilities

the OAPE team currently owns the OperatorSDK and accompanying components. They will be expected to facilitate any technical requirements of sustaining engineering to enable successful transition.

Success Criteria

The goal is to have sustaining engineering successfully transition ownership of the operator sdk repository downstream by end of Q2 '25. Success could be measured by having them release an bug fix or cve fix for the operator sdk binary... however, this might be unlikely given how stable the binary is.

Results

Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.