From cdbbb118fdc0cb15852b98ace7a5b8addc779f00 Mon Sep 17 00:00:00 2001 From: adriancuadrado <29214635+adriancuadrado@users.noreply.github.com> Date: Thu, 28 Nov 2024 19:43:31 +0100 Subject: [PATCH] Fixed broken link Signed-off-by: adriancuadrado <29214635+adriancuadrado@users.noreply.github.com> --- SPEC.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SPEC.md b/SPEC.md index d7ba7d77..01801148 100644 --- a/SPEC.md +++ b/SPEC.md @@ -107,8 +107,8 @@ require this. A network configuration consists of a JSON object with the following keys: -- `cniVersion` (string): [Semantic Version 2.0](https://semver.org) of CNI specification to which this configuration list and all the individual configurations conform. Currently "1.1.0" -- `cniVersions` (string list): List of all CNI versions which this configuration supports. See [version selection](#version-selection) below. +- `cniVersion` (string): [Semantic Version 2.0](https://semver.org) of CNI specification to which this configuration list and all the individual configurations conform. Currently "1.1.0". +- `cniVersions` (string list): List of all CNI versions which this configuration supports. See [version considerations](#version-considerations) below. - `name` (string): Network name. This should be unique across all network configurations on a host (or other administrative domain). Must start with an alphanumeric character, optionally followed by any combination of one or more alphanumeric characters, underscore, dot (.) or hyphen (-). Must not contain characters disallowed in file paths. - `disableCheck` (boolean): Either `true` or `false`. If `disableCheck` is `true`, runtimes must not call `CHECK` for this network configuration list. This allows an administrator to prevent `CHECK`ing where a combination of plugins is known to return spurious errors. - `disableGC` (boolean): Either `true` or `false`. If `disableGC` is `true`, runtimes must not call `GC` for this network configuration list. This allows an administrator to prevent `GC`ing when it is known that garbage collection may have undesired effects (e.g. shared configuration between multiple runtimes).