Skip to content

🚀 Release v1.10.0-beta.0 #11989

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.

Sign up for GitHub

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

Jump to bottom
Merged
k8s-ci-robot merged 1 commit into from
Mar 18, 2025
Merged

🚀 Release v1.10.0-beta.0 #11989

k8s-ci-robot merged 1 commit into from
Mar 18, 2025

Conversation

@chandankumar4
Copy link
Contributor

@chandankumar4 chandankumar4 commented Mar 18, 2025

What this PR does / why we need it:

  • Release notes for v1.10.0-beta.0

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Part of: #11656

/area release

@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 18, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 18, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@k8s-ci-robot k8s-ci-robot added area/release Issues or PRs related to releasing cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Mar 18, 2025
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 18, 2025
chandankumar4
chandankumar4 commented Mar 18, 2025
View reviewed changes
CHANGELOG/v1.10.0-beta.0.md Outdated
Comment on lines 5 to 10
- Management Cluster: v1.**X**.x -> v1.**X**.x
- Workload Cluster: v1.**X**.x -> v1.**X**.x

[More information about version support can be found here](https://cluster-api.sigs.k8s.io/reference/versions.html)

## Deprecations and Removals
Copy link
Contributor Author

@chandankumar4 chandankumar4 Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sbueringer could you help me with K8s version support and "Deprecations and Removals" if any? Thanks

Copy link
Contributor

@mboersma mboersma Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#11679 "⚠️ Remove deprecated flag for old infra machine naming" should probably be in here.

Copy link
Contributor

@mboersma mboersma Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also:

For k8s version support, in 1.9.x it's:
Management Cluster: v1.28.x -> v1.32.x
Workload Cluster: v1.26.x -> v1.32.x

Has CAPI officially added v1.33.x support? I see #11496.

Copy link
Member

@sbueringer sbueringer Mar 18, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest, I don't have the time today to write these sections properly. What about we leave them empty for the beta?

(I'm planning to do it this week or next week though)

Copy link
Member

@sbueringer sbueringer Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has CAPI officially added v1.33.x support? I see #11496.

No. This only happens in the v1.10.1 release after v1.33.0 is out

Copy link
Contributor Author

@chandankumar4 chandankumar4 Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, Removed the section from release notes.

Copy link
Contributor

@mboersma mboersma Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we leave the section header ## Deprecations and Removals there but just put TBD? Might be less confusing if people are looking for that in the release notes, but lgtm either way.

Copy link
Member

@sbueringer sbueringer Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have the time today to write these sections properly. What about we leave them empty for the beta?

One addition. Usually this takes me half a day or a day. Basically digging through all PRs to figure out what to add under highlights & deprecations.

Copy link
Member

@sbueringer sbueringer Mar 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added highlights / deprecation & removals to the beta.0 GitHub release

Copy link
Member

@sbueringer sbueringer Mar 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also shared them here for subsequent releases: #11656 (comment)

@chandankumar4 chandankumar4 force-pushed the release-v1.10.0-beta.0 branch from 462e6df to 8cef9ad Compare March 18, 2025 15:57
@chandankumar4 chandankumar4 marked this pull request as ready for review March 18, 2025 15:57
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 18, 2025
@k8s-ci-robot k8s-ci-robot requested a review from Sunnatillo March 18, 2025 15:57
@sbueringer
Copy link
Member

sbueringer commented Mar 18, 2025

@mboersma

We just merged #11990

Would be great if we can also wait for #11986 to be merged (should happen soon and helps to stabilize CI a bit)

You can already update the release notes (manually) to contain both

@chandankumar4
🚀 Release v1.10.0-beta.0
ba6d71d 
Signed-off-by: chandankumar4 <chandan.kr404@gmail.com>
@chandankumar4 chandankumar4 force-pushed the release-v1.10.0-beta.0 branch from 8cef9ad to ba6d71d Compare March 18, 2025 16:10
@chandankumar4
Copy link
Contributor Author

chandankumar4 commented Mar 18, 2025

@mboersma

We just merged #11990

Would be great if we can also wait for #11986 to be merged (should happen soon and helps to stabilize CI a bit)

You can already update the release notes (manually) to contain both

Added both PR

@sbueringer
Copy link
Member

sbueringer commented Mar 18, 2025

/lgtm
/approve

All good from my side

/hold
Feel free to merge

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 18, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 18, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 18, 2025

LGTM label has been added.

DetailsGit tree hash: 06a5516b653f7b1e4d399ec5d4ed57c92ef93a5e

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2025
mboersma
mboersma approved these changes Mar 18, 2025
View reviewed changes
Copy link
Contributor

@mboersma mboersma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@mboersma
Copy link
Contributor

mboersma commented Mar 18, 2025

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 18, 2025
@k8s-ci-robot k8s-ci-robot merged commit 2303bd0 into kubernetes-sigs:main Mar 18, 2025
17 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.10 milestone Mar 18, 2025
@chandankumar4 chandankumar4 deleted the release-v1.10.0-beta.0 branch March 18, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sbueringer sbueringer sbueringer left review comments

@cahillsf cahillsf Awaiting requested review from cahillsf

@cprivitere cprivitere Awaiting requested review from cprivitere

@Sunnatillo Sunnatillo Awaiting requested review from Sunnatillo

+1 more reviewer

@mboersma mboersma mboersma approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@mboersma mboersma

@sbueringer sbueringer

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release Issues or PRs related to releasing cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

v1.10

Development

Successfully merging this pull request may close these issues.

4 participants

@chandankumar4 @k8s-ci-robot @sbueringer @mboersma