Meta Issue for k8s 1.34 bump

Meta Issue for k8s 1.34 bump

In order to bump Operator SDK to support Kubernetes 1.34 there are a few dependencies we rely on making the bump first.
This issue is meant to help track all dependencies and the status of their bumps.

Order of dependency bumps

Step 1: upgrade controller-runtime, controller-tools, helm, and operator-framework/operator-manifest-tools(can be done in parallel)

• sigs.k8s.io/controller-runtime https://github.com/kubernetes-sigs/controller-runtime/pull/3300
• sigs.k8s.io/controller-tools https://github.com/kubernetes-sigs/controller-tools/pull/1266
• operator-framework/operator-manifest-tools https://github.com/operator-framework/operator-manifest-tools/pull/96

Step 2: upgrade operator-framework/api (can be done immediately after controller-runtime & controller-tools)

• operator-framework/api https://github.com/operator-framework/api/pull/447

Step 3.1: upgrade operator-framework/operator-registry and operator-framework/operator-lib (can be done immediately after operator-framework/api)

• operator-framework/operator-registry https://github.com/operator-framework/operator-registry/pull/1772
• operator-framework/operator-lib https://github.com/operator-framework/operator-lib/pull/254

Step 3.2: upgrade kubebuilder

• sigs.k8s.io/kubebuilder/v4 https://github.com/kubernetes-sigs/kubebuilder/pull/5146

Step 4: upgrade operator-framework plugins

• operator-framework/ansible-operator-plugins

Step 5: upgrade operator-framework/operator-sdk dependencies

• Bump Ginkgo/v2 and Kubebuilder 1.34
• Bump SDK to use k8s 1.34

Start with the unchecked Step 4 and Step 5 items in this meta issue, then review the linked dependency bumps completed in Steps 1–3. Track the ansible-operator-plugins, Ginkgo/v2, Kubebuilder, and Kubernetes 1.34 updates, and mark the remaining checklist items complete when the Operator SDK dependencies support Kubernetes 1.34.