Skip to content

Release Notes draft for k/k v1.33.0-rc.1 #2765

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

Conversation

sreeram-venkitesh
Copy link
Member

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Release notes for v1.33-rc.1

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 16, 2025
@k8s-ci-robot k8s-ci-robot requested a review from rayandas April 16, 2025 12:24
@k8s-ci-robot k8s-ci-robot added the area/release-team Issues or PRs related to the release-team subproject label Apr 16, 2025
@k8s-ci-robot k8s-ci-robot requested a review from rytswd April 16, 2025 12:24
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. needs-priority size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Apr 16, 2025
@rayandas
Copy link
Member

@sreeram-venkitesh There's a lint issue. Could you please run krel release-notes validate --path-to-release-notes releases/release-1.33/release-notes/maps and fix the lint issues?

If you are also using the feature gate `KubeletCrashLoopBackOffMax` with a configured
per-node `CrashLoopBackOff.MaxContainerRestartPeriod`, the effective kubelet configuration
will follow the conflict resolution policy described further in the documentation
[here](TODO:link).
Copy link
Member Author

Choose a reason for hiding this comment

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

This link has not been updated in the PR yet. We can ping the author about it.

Copy link
Member

Choose a reason for hiding this comment

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

I've updated it in the final release note draft. Don't worry about it.

@sreeram-venkitesh
Copy link
Member Author

@rayandas The lint issue is from this multiline release note not being wrapped in quotes. Can I update this manually in releases/release-1.33/release-notes/maps/pr-122550-map.yaml?

image

@@ -12,7 +12,7 @@

### Deprecation

- The EndpointSlice `hints` field has graduated to GA. The beta annotation `service.kubernetes.io/topology-mode` is now considered deprecated and will not graduate to GA. It remains operational for backward compatibility. Users are encouraged to use the `spec.trafficDistribution` field in the Service API for topology-aware routing configuration. ([#130742](https://github.com/kubernetes/kubernetes/pull/130742), [@gauravkghildiyal](https://github.com/gauravkghildiyal)) [SIG Network]
- The EndpointSlice `hints` field has graduated to GA. The beta annotation `service.kubernetes.io/topology-mode` is now considered deprecated and will not graduate to GA. It remains operational for backward compatibility. Users are encouraged to use the `spec.trafficDistribution` field in the Service API for topology-aware routing configuration. ([#130742](https://github.com/kubernetes/kubernetes/pull/130742), [@gauravkghildiyal](https://github.com/gauravkghildiyal))
- The `StorageCapacityScoring` feature gate was added to score nodes by available storage capacity. It's in alpha and disabled by default. The `VolumeCapacityPriority` alpha feature was replaced with this, and the default behavior was changed. The `VolumeCapacityPriority` preferred a node with the least allocatable, but the `StorageCapacityScoring` preferred a node with the maximum allocatable. See [KEP-4049](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/4049-storage-capacity-scoring-of-nodes-for-dynamic-provisioning/README.md) for details. ([#128184](https://github.com/kubernetes/kubernetes/pull/128184), [@cupnes](https://github.com/cupnes)) [SIG Scheduling, Storage and Testing]
Copy link
Member

Choose a reason for hiding this comment

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

The SIGs are being removed for a lot of notes. Are you using krel latest version? This was a bug in a previous version as I can recall.

@rayandas
Copy link
Member

The lint issue is from this multiline release note not being wrapped in quotes. Can I update this manually in releases/release-1.33/release-notes/maps/pr-122550-map.yaml?

@sreeram-venkitesh Yeah update it manually and push it.

@sreeram-venkitesh
Copy link
Member Author

@rayandas I've fixed the lint issues with missing punctuations and also added the SIGs back. I had installed the latest version of krel, not sure why the SIGs were removed.

@sreeram-venkitesh sreeram-venkitesh force-pushed the release-notes-draft-v1.33.0-rc.1 branch from 41ed520 to edd0bcf Compare April 17, 2025 15:48
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 18, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: npolshakova, sreeram-venkitesh

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 /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 Apr 18, 2025
@npolshakova npolshakova requested a review from rayandas April 18, 2025 14:29
@k8s-ci-robot k8s-ci-robot merged commit 0be56c6 into kubernetes:master Apr 18, 2025
3 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.33 milestone Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-team Issues or PRs related to the release-team subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants