-
Notifications
You must be signed in to change notification settings - Fork 64
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
🌱 Bump Cluster API to v1.5.0-rc.0 #186
Conversation
/hold waiting for the new version to be released. |
e05ea81
to
8b612ab
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Fedosin thanks for the PR, overall looks good to me, only one missing update I noticed based on the migration doc https://main.cluster-api.sigs.k8s.io/developer/providers/migrations/v1.4-to-v1.5.html#go-version and few more suggestions inline:
- we need to bump CT in https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/hack/tools/go.mod#L11 to v0.12.x
/retitle 🌱 Bump Cluster API to v1.5.0-beta.1
{ | ||
GroupVersion: "cert-manager.io/v1", | ||
APIResources: []metav1.APIResource{ | ||
{Kind: "Certificate", Namespaced: true}, | ||
{Kind: "Issuer", Namespaced: true}, | ||
}, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we removing this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are 2 reasons for that:
- In clusterctl they explicitly declare that this function should not return cert-manager objects. It's better to keep things consistent with cluster-api.
- After upgrading to controller-runtime v0.15.0 some tests fail because they need cert-manager CRDs installed (I still don't understand why it works in the previous versions). I don't want to add cert-manager to the operator dependencies, so I just decided to remove the section.
I updated container images for e2e tests to make them work with golang 1.20: kubernetes/test-infra#30077 |
/retest |
We can always merge the rc bump and give the CI time to run longer with it to see if there are problems, so that whenever actual 1.5.0 comes out, it is just a matter of updating go.mod, nothing more. |
/retitle 🌱 Bump Cluster API to v1.5.0-rc.0 |
@furkatgofurov7 I'm okay to merge #187 first and then I'll update my PR. |
@Fedosin sure, it should be ready to merge now, PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @Fedosin!
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: furkatgofurov7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: d2fdc8b097eec310ad623578af7077072fa9544c
|
/hold cancel We will bump to v1.5 CAPI once out (fairly straightforward then this one), this we can take in now. |
What this PR does / why we need it:
This PR update CAPI operator to the latest Cluster API version.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #183