Skip to content

Commit 2b93fbd

Browse files
committed
Improve drawbacks section
1 parent 5a71bb5 commit 2b93fbd

File tree

1 file changed

+11
-4
lines changed
  • keps/sig-node/4817-resource-claim-device-status

1 file changed

+11
-4
lines changed

keps/sig-node/4817-resource-claim-device-status/README.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -607,11 +607,18 @@ N/A
607607

608608
## Drawbacks
609609

610-
If the Network device (network interface) characteristics (e.g. IP) and status
610+
If the network device (network interface) characteristics (e.g. IP) and status
611611
is reported as part of the `Resource.Claim.Status`, it should be ensured the
612-
`ResourceClaim` is not used by several `Pod` at a time. Additionally, if a
613-
controller needs to gather IPs for a specific network to which Pods are
614-
attached via networking devices, it will need to query each `Pod` and then
612+
`ResourceClaim` is not used by several `Pod` at a time.
613+
614+
As the network device characteristics are reported in the `ResourceClaim.Status`,
615+
the downward API will not provide additional fields to expose those characteristics.
616+
For example, `Pod.Status.PodIPs` can be provided as an environment variable to
617+
the running containers while `ResourceClaim.Status.Devices['KEY'].NetworkData.Addresses`
618+
will not be available.
619+
620+
Furthermore, if a controller needs to gather IPs for a specific network to which
621+
Pods are attached via networking devices, it will need to query each `Pod` and then
615622
access the corresponding `ResourceClaim` for every Pod.
616623

617624
## Alternatives

0 commit comments

Comments
 (0)