Meta Issue for k8s 1.30 bump

[Neo2308]

Meta Issue for k8s 1.30 bump

In order to bump Operator SDK to support Kubernetes 1.30 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/releases/tag/v0.18.0)
• sigs.k8s.io/controller-tools (https://github.com/kubernetes-sigs/controller-tools/releases/tag/v0.15.0)
• operator-framework/operator-manifest-tools (Updating k8s to 1.30 & go to 1.22 operator-manifest-tools#57) (https://github.com/operator-framework/operator-manifest-tools/releases/tag/v0.7.0)

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

• operator-framework/api (K8s 1.30 version update and go 1.22 api#322) (https://github.com/operator-framework/api/releases/tag/v0.24.0)

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 (Bump k8s libraries to v0.30.0 operator-registry#1297) (https://github.com/operator-framework/operator-registry/releases/tag/v1.42.0)
• operator-framework/operator-lib (bump go to 1.22, k8s deps to 0.30.0 operator-lib#176) (https://github.com/operator-framework/operator-lib/releases/tag/v0.14.0)

Step 3.2: upgrade kubebuilder

• sigs.k8s.io/kubebuilder/v4 (✨ Upgrade controller-runtime from v0.17.3 to v0.18.2 kubernetes-sigs/kubebuilder#3912) (https://github.com/kubernetes-sigs/kubebuilder/releases/tag/v4.1.1)

Step 4: upgrade operator-framework plugins

• operator-framework/ansible-operator-plugins ({WIP} Bump k8s dependencies to 1.30 ansible-operator-plugins#102)
• operator-framework/helm-operator-plugins (bump go 1.22 and k8s 1.30 helm-operator-plugins#337 & Bump Kubebuilder to v4 helm-operator-plugins#346)
• operator-framework/java-operator-plugins (Bump to go 1.22, k8s 1.30 & kubebuilder 4.0 java-operator-plugins#151) (https://github.com/operator-framework/java-operator-plugins/releases/tag/v0.11.0)

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

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

[Neo2308]

Copied from #6651
Removed "sigs.k8s.io/kubebuilder-declarative-pattern" based on #6651 (comment)

[Neo2308]

K8s 1.30 support for kubebuilder would be coming post the major bump in kubebuilder version.
Ref: kubernetes-sigs/kubebuilder#3622

[acornett21]

Updated the description to remove the helm operator plugin since we are dropping hybrid support

[Neo2308]

@acornett21 wouldn't we still need to update the helm operator plugin version in the operator-sdk and hence have to update k8s/controller runtime versions in the helm repo and cut new versions?

[acornett21]

@Neo2308 we still need to keep the helm-operator-plugin repo up to date (though since other projects depend on that that move at a quicker pace, you probably no longer need to worry about it for your needs), but it no longer needs to be a dependency of this project, since this project still contains the helm operator code. Confusing, I know, I assumed all the helm code was in the plugin repo, but it is not.

[acornett21]

It looks like we'll have to update to kubebuilder v4 for this and use version 4.1.1, unless I'm missing something.