Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta Issue for k8s 1.31 bump #6816

Closed
10 tasks done
Neo2308 opened this issue Aug 20, 2024 · 4 comments
Closed
10 tasks done

Meta Issue for k8s 1.31 bump #6816

Neo2308 opened this issue Aug 20, 2024 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Neo2308
Copy link
Contributor

Neo2308 commented Aug 20, 2024

Meta Issue for k8s 1.31 bump

In order to bump Operator SDK to support Kubernetes 1.31 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)

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

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

Step 3.2: upgrade kubebuilder

Step 4: upgrade operator-framework plugins

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

  • Bump Ginkgo/v2 and Kubebuilder 1.31
  • Bump SDK to use k8s 1.31
@Neo2308
Copy link
Contributor Author

Neo2308 commented Aug 20, 2024

Copied from #6730
Changed "sigs.k8s.io/kubebuilder/v3" to "sigs.k8s.io/kubebuilder/v4" based on #6730 (comment)

@acornett21
Copy link
Contributor

removed helm and java plugin.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 4, 2025
@acornett21
Copy link
Contributor

This was resolved in the below release
https://github.com/operator-framework/operator-sdk/releases/tag/v1.39.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants