chore(deps): update module github.com/containernetworking/cni to v1.3.0

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/containernetworking/cni	v1.1.2 -> v1.3.0

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

containernetworking/cni (github.com/containernetworking/cni)

v1.3.0

Compare Source

What's Changed

• RFC - Support safe subdirectory-based plugin conf loading by @​bleggett in #​1052

This adds a new config flag loadPluginsFromFolder - if present, for a given named network bar, plugin configuration objects will be loaded from <path-to-bar-network-config-file>/bar/xxx.conf. This may be useful for vendors providing chained plugins: you can add your plugin to a chain without needing to edit the file in-place.

New Contributors

• @​bleggett made their first contribution in #​1052

Full Changelog: containernetworking/cni@v1.2.3...v1.3.0

v1.2.3: libcni v1.2.3

Compare Source

This is a minor release to correct a divergence between the specification and libcni. In this case, the specification was updated, as it concerns a new feature, GC, that is not yet deployed.

What's Changed

• SPEC, libcni: harmonize GC valid-attachment key by @​squeed in #​1103

v1.2.2: libcni v1.2.2

Compare Source

What's Changed

• libcni: remove use of Masterminds/semver by @​squeed in #​1100

Full Changelog: containernetworking/cni@v1.2.1...v1.2.2

v1.2.1: CNI Spec v1.1 / libcni v1.2.1

Compare Source

This is a minor release that fixes some small bugs:

Improvements

• (#​1098). SPEC: add warning about preserving shared resources for GC
• (#​1090). Spec, libcni: add disableGC flag This allows administrators to disable garbage collection in exceptional circumstances, such as multiple runtimes sharing a network configuration.

Bug fixes:

• (#​1097). Fix faulty json.Marshal behavior for embeds types.NetConf Fix #​1096
• (#​1095). libcni: always delete the cache on conflist for CNI DEL This aligns the call with DelNetwork, and allows CRIO tests to bump

v1.2.0: CNI spec v1.1 / libcni v1.2.0

Compare Source

This is libcni v1.2.0, which releases the new CNI spec version v1.1.0.

Major changes:

GC verb

The GC verb allows runtimes to specify the set of known-good attachments, allowing plugins to clean up stale and leaked resources such as IPAM reservations. Libcni will also synthesize a CNI DEL for any stale cached attachments, so all users will have a form of GC, even if their plugins do not support CNI v1.1

STATUS verb

The STATUS verb allows a plugin to report its readiness to accept ADD requests. Runtimes such as containerd and cri-o will no longer have to rely merely on the presence of a CNI configuration file to determine network readiness.

Version negotiation

CNI configurations may now contain multiple versions, so that an administrator can opportunistically update the protocol version without breaking older runtimes:

{
  "cniVersion": "1.0.0",
  "cniVersions": ["1.0.0", "1.1.0"]
}

New fields

A number of new fields have been added to the result type:

• (#​1060). Add MTU to CNI result
• (#​1068). Add Scope property for routes Fixes: #​598
• (#​1069). Add SocketPath/PciID to Interface struct This is to resolve: #​1050
• (#​1062). Add table ID property for routes Fixes #​1061
• (#​1041). Add route attributes - MTU, AdvMSS, Priority

Other improvements

• (#​911). libcni: add specific type for CHECK not supported
• (#​1072). tolerate invalid cni caches for deletion
• (#​1054). Add Version() to CNI interface

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.