Mike Zappa

spec,libcni: add metadata field to Interface struct for CNI Result

2

This PR resolves: #1050 This PR adds an optional 'metadata' field (map[string]string) to the Interfaces struct. ``` type Interface struct { Name string `json:"name"` Mac string `json:"mac,omitempty"` Sandbox string `json:"sandbox,omitempty"`...

spec: add attachment and endpoint definitions to specification

1

We started this back in #903 however I am closing that and opening this one. Two comments by @dcbw @squeed @henry118 should be reviewed.

Add Version to CNI interface

2

When looking at how to integrate STATUS/GC in containerd I noticed that Version was not exposed on the CNI Interface. I am not certain if that was intended? I didn't...

INIT Verb for CNI 1.1

5

We have come to the conclusion that INIT should be implemented in the CNI. To do this we need to do the following. 1. Come up with use cases 2....

I decided to move the CI changes to a different PR. Will rebase the other PR's with this on merge.

[DRAFT] Status should ensure CNI Network Configuration and CNI binaries in the NetConf are present to set Network Ready

1

It seems like issues are popping up where the CNI network configuration is present but no CNI binaries present and the node is being marked ready.

The CNI maintainer intend on deprecating the loopback plugin. This should be called before or after the Setup function in containerd.

[KNI] Kubernetes Network reImagined (Interface)

4

### Enhancement Description - One-line enhancement description (can be used as a release note): This is to create the KNI which is a foundational k8s network API - Kubernetes Enhancement...

Add support to set loopback to up

9

The CNI maintainers intend on deprecating the loopback plugin. This approach where we set the lo interface to up is similar to what CRI-O does. We (@mikebrow ) decided to...