Epic Goal

Operator-SDK supports Kube 1.25 (K8s GA: Aug 23, 2022) for OCP 4.12 Release (Code Freeze: TBD, 2022, GA: TBD, 2022).

Why is this important?

Operator SDK needs to support the latest features of Kubernetes since that operator developers expect to be able to use them shortly after the release is made.

As OCP is moving to align with k8s as 3 releases per year, it's important Operator SDK also keeps in sync with the k8s release version.

Acceptance Criteria

• in scope: Operator developers have a release of the SDK that supports Kubernetes 1.25
• in scope: Update dependencies and fix up anything as a result of breaking changes.
• in scope: Requirement figure out generic framework for alpha and beta releases of controller-runtime and kubebuilder to bring them into the sdk
• out of scope: Additional work in SDK related to Kubernetes 1.25 new features is out of scope.
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. [external] Require controller-runtime release that supports 1.25
2. [external] Require Helm release that supports 1.25
3. [external] Require kubebuilder release that scaffolds projects using 1.25
4. [internal] Require operator-framework/api release that supports 1.25

Open questions::

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>