Blog with DRA updates in 1.34 #51488
Conversation
k8s-ci-robot
added
do-not-merge/work-in-progress
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/area blog |
k8s-ci-robot
added
the
area/blog
|
Hi @mortent happy to see this PR! Thank you, |
|
@graz-dev This will be the blog post for all DRA features in 1.34. We usually do one post that covers everything new in DRA for a release, rather than having several individual ones. The one for 1.33 is here: https://kubernetes.io/blog/2025/05/01/kubernetes-v1-33-dra-updates/ |
|
@graz-dev Yeah, that is the plan. |
|
/sig release |
k8s-ci-robot
added
the
sig/release
|
Hi @mortent 👋 -- this is Graz from the v1.34 Communications Team! Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: Friday 8th August 2025. We ask you to have the blog in non-draft state, and all write-up to be complete. If you have any questions or need help, please don't hesitate to reach out to me or any of the Communications Team members. We are here to help you! |
k8s-ci-robot
added
language/en
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
There was a problem hiding this comment.
A comment about style.
Overall, we usually write concepts in italics (eg extended resource mapping).
We might also use Title Case but only where we abbreviate. So it's OK to write Dynamic Resource Allocation (DRA), but Admin Access should be admin access (or better, admin access restriction because admin access as a general concept isn't new to v1.34). We don't put admin access restriction in title case unless people want to abbreviate it ("AAR", perhaps).
k8s-ci-robot
added
size/L
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
Do we have the SIG approval on the content of this PR? |
|
SIG Node should give the SIG approval here. Maybe @haircommander or @mrunalp can take a look? |
|
If it has to be a sig then probably SIG Node. But it spans a few sigs...certainly it has WG approval from WG dev mgmt. |
|
LGTM from SIG node side |
|
/lgtm cancel because of that hyperlink. I'm happy with the tech content; it's high level enough that I feel confident and won't ask the WG for a tech review. |
k8s-ci-robot
removed
the
lgtm
|
|
||
| Starting with Kubernetes 1.34, DRA is enabled by default; DRA features that have reached beta are also enabled by default. | ||
| That's because the default API version for DRA is now the stable `v1` version, and not the earlier versions | ||
| (eg: `v1beta1` or `v1beta2`) that needed explicit opt in. |
There was a problem hiding this comment.
This is good enough for now because it is a true state for all current beta DRA features. But let's remember that at least DeviceTaints has its own, separate type and won't be enabled by default even at beta because that type won't be (shouldn't be?) in v1 at that point.
|
|
||
| ## Acknowledgments | ||
|
|
||
| A huge thanks to the new contributors to DRA this cycle: |
There was a problem hiding this comment.
Some listed here have been contributing to previous releases, but wasn't included in the list in the 1.33 blog post.
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 4b35570d1ef5e691d8591fbb59007a69ff797560
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: graz-dev 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 |
k8s-ci-robot
added
the
approved
Description
Blog that provides updates on the changes in DRA for 1.34. This includes information about core DRA graduating to GA, new features promoted to Beta, new Alpha features, and a short outline of the plans for DRA for 1.35.
Issue
Closes: #