Skip to content

Commit ba21b04

Browse files
committed
update example for reserved network types
1 parent c9f2407 commit ba21b04

File tree

2 files changed

+16
-8
lines changed

2 files changed

+16
-8
lines changed

Diff for: keps/sig-network/4962-network-topology-standard/README.md

+16-8
Original file line numberDiff line numberDiff line change
@@ -254,29 +254,37 @@ If provided, Network QoS Annotations can be used to refine and enhance the detai
254254

255255
#### Example of Network Topology Labels with reserved network types:
256256

257+
Consider the following network topology:
258+
259+
![Netwotk topology with reserved network types](./img/topo-reserved-labels.png)
260+
261+
Let's examine node `vm12` as an example. This node is connected to NVSwitch `nvl10` and network switch sw11, which in turn is connected to switches `sw21` and `sw31`.
262+
In this case, the node labels would be:
257263
```
258-
network.topology.kubernetes.io/accelerator: nvl72-a
259-
network.topology.kubernetes.io/block: block-b
260-
network.topology.kubernetes.io/datacenter: dc-c
261-
network.topology.kubernetes.io/zone: zone-d
264+
network.topology.kubernetes.io/accelerator: nvl10
265+
network.topology.kubernetes.io/block: sw11
266+
network.topology.kubernetes.io/datacenter: sw21
267+
network.topology.kubernetes.io/zone: sw31
262268
```
263269

264270
#### Example of Network QoS Annotations that complements the example above:
271+
272+
If we have additional information such as latency and/or bandwidth between the node and the switches, it can be provided in an annotation:
265273
```
266274
network.qos.kubernetes.io/switches: {
267-
"nvl72-a": {
275+
"nvl10": {
268276
"latency": "2us",
269277
"bandwidth": "100Gbps"
270278
},
271-
"block-b": {
279+
"sw11": {
272280
"latency": "50us",
273281
"bandwidth": "40Gbps"
274282
},
275-
"dc-c": {
283+
"sw21": {
276284
"latency": "500us",
277285
"bandwidth": "20Gbps"
278286
},
279-
"zone-d": {
287+
"sw31": {
280288
"latency": "1ms",
281289
"bandwidth": "10Gbps"
282290
}
Loading

0 commit comments

Comments
 (0)