Skip to content

Commit 1e03090

Browse files
committed
publish kubernetes-v1-34-dra-134-updates
1 parent a188498 commit 1e03090

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

content/en/blog/_posts/XXXX-XX-XX-dra-134-update.md renamed to content/en/blog/_posts/2025-09-01-dra-134-update.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
---
22
layout: blog
33
title: "Kubernetes v1.34: DRA has graduated to GA"
4-
slug: dra-134-updates
5-
draft: true
6-
date: XXXX-XX-XX
4+
slug: kubernetes-v1-34-dra-updates
5+
date: 2025-09-01T10:30:00-08:00
76
author: >
87
The DRA team
98
---
@@ -70,6 +69,7 @@ device sharing model where multiple, independent resource claims from unrelated
7069
pods can each be allocated a share of the same underlying physical device. This new capability is managed through optional,
7170
administrator-defined sharing policies that govern how a device's total capacity is divided and enforced by the platform for
7271
each request. This allows for sharing of devices in scenarios where pre-defined partitions are not viable.
72+
A blog about this feature is coming soon.
7373

7474
[Binding conditions](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/#binding-conditions) improve scheduling
7575
reliability for certain classes of devices by allowing the Kubernetes scheduler to delay binding a pod to a node until its
@@ -80,6 +80,7 @@ readiness before the pod is committed to a node.
8080
_Resource health status_ for DRA improves observability by exposing the health status of devices allocated to a Pod via Pod Status.
8181
This works whether the device is allocated through DRA or Device Plugin. This makes it easier to understand the cause of an
8282
unhealthy device and respond properly.
83+
A blog about this feature is coming soon.
8384

8485
## What’s next?
8586

0 commit comments

Comments
 (0)