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.30 bump #6730

Open
12 tasks done
Neo2308 opened this issue Apr 26, 2024 · 9 comments · Fixed by #6848 · May be fixed by #6862
Open
12 tasks done

Meta Issue for k8s 1.30 bump #6730

Neo2308 opened this issue Apr 26, 2024 · 9 comments · Fixed by #6848 · May be fixed by #6862
Labels
dependencies Pull requests that update a dependency file
Milestone

Comments

@Neo2308
Copy link
Contributor

Neo2308 commented Apr 26, 2024

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)

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.30
  • Bump SDK to use k8s 1.30
@Neo2308
Copy link
Contributor Author

Neo2308 commented Apr 26, 2024

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

@Neo2308
Copy link
Contributor Author

Neo2308 commented May 22, 2024

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

@acornett21
Copy link
Contributor

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

@Neo2308
Copy link
Contributor Author

Neo2308 commented Aug 27, 2024

@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
Copy link
Contributor

@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
Copy link
Contributor

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

@acornett21
Copy link
Contributor

Released v1.36.0 of the ansible plugin.

https://github.com/operator-framework/ansible-operator-plugins/releases/tag/v1.36.0

@acornett21
Copy link
Contributor

acornett21 commented Nov 8, 2024

Re-opening as this got auto-closed, items still needed:

  • migration docs
  • changelog docs
  • new ansible version with rbac metrics scaffolding code

@acornett21 acornett21 reopened this Nov 8, 2024
@arf1372
Copy link

arf1372 commented Nov 9, 2024

I need this update. When do you think this would happen? Should I use Kubebuilder in the meantime?
I'm using k3s/helm-controller and it depends on controller-runtime 1.30. Hence my code gets broken and I can't develop my operator by now.
Apologies for my limited english. I really need to understand how can I do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment