-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Kubernetes 1.30 release blog #45691
Kubernetes 1.30 release blog #45691
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
LGTM label has been added. Git tree hash: 704d247c4b1fd578175a29c1952b40e05ba2f873
|
@kcmartin I'll edit the PR description to change: -WIP - Draft - Release announcement blog article from the Comms team for Kubernetes 1.30
+Add release announcement blog article from the Comms team for Kubernetes 1.30 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
Co-authored-by: Rey Lejano <rlejano@gmail.com>
/lgtm |
LGTM label has been added. Git tree hash: 27d1b16085cbb3dfc24c0a942596b2f571852a04
|
/lgtm The author attribution will look right once this merges. |
LGTM label has been added. Git tree hash: 2679efe7be8f0233b2786280c74a200978caf20e
|
/remove-hold |
I don't see "ceph" anywhere in the release notes? IMHO same-cycle is really late for a removal that didn't previously declare a timeline 😅 If we're saying we're not publishing it because it was previously announced as deprecated in past notes ... it's different now that we're actually planning to remove it? To find out when it was going to be removed I had to ask the SIG, it was in a SIG Google sheet. Users are mostly not going to react to a removal with no deadline. |
About ceph: let's find a good place to have that discussion, and then link from this PR to that good place. |
🛑 DO NOT MERGE 🛑 UNTIL KUBERNETES 1.30 IS RELEASED
Add release announcement blog article from the Comms team for Kubernetes 1.30
To do: