File tree Expand file tree Collapse file tree 1 file changed +11
-4
lines changed
keps/sig-node/4817-resource-claim-device-status Expand file tree Collapse file tree 1 file changed +11
-4
lines changed Original file line number Diff line number Diff line change @@ -607,11 +607,18 @@ N/A
607
607
608
608
# # Drawbacks
609
609
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
611
611
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
615
622
access the corresponding `ResourceClaim` for every Pod.
616
623
617
624
# # Alternatives
You can’t perform that action at this time.
0 commit comments