You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SPEC.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ Plugins that consume any of these configuration keys should respect their intend
148
148
Plugins may define additional fields that they accept and may generate an error if called with unknown fields. Runtimes must preserve unknown fields in plugin configuration objects when transforming for execution.
149
149
150
150
#### Example configuration
151
-
Network configuration with no inlined plugin confs, and two loaded plugin confs:
151
+
The following is an example file-based JSON representation of a network configuration `dbnet`with no inlined plugin configurations, and two external aggregated plugin configurations (`bridge` and `tuning`) in JSON format:
152
152
`/etc/cni/net.d/10-dbnet.conf`:
153
153
```jsonc
154
154
{
@@ -195,7 +195,7 @@ Network configuration with no inlined plugin confs, and two loaded plugin confs:
195
195
}
196
196
```
197
197
198
-
Network configuration with one inlined plugin conf, and one loaded plugin conf:
198
+
The following is an example file-based JSON representation of a network configuration `dbnet`with one inlined plugin configuration (`bridge`), and one external aggregated plugin configuration `tuning` in JSON format:
199
199
`/etc/cni/net.d/10-dbnet.conf`:
200
200
```jsonc
201
201
{
@@ -240,7 +240,7 @@ Network configuration with one inlined plugin conf, and one loaded plugin conf:
240
240
}
241
241
```
242
242
243
-
Network configuration with one inlined plugin conf, and no loaded plugin conf:
243
+
The following is an example file-based JSON representation of a network configuration `dbnet`with one inlined plugin configuration (`bridge`), and no external aggregated plugin configs
0 commit comments