cni

cni copied to clipboard

Data getting lost between Flannel and CNI.

4

**Issue** - I have a single master - single worker cluster built using two servers with RHEL 8.6, Kubernetes 1.23.7 and Flannel 1.1.0. An NGINX ingress controller is configured with...

schintalapudi

"failed to call cni.Setup: plugin type=\"bridge\" failed (add): running [/usr/sbin/iptables "

1

```bash > nerdctl --namespace=nerdctl-test run --rm --net host myregistry.domain.com:5001/stargz-containers/alpine:3.13-org > > nerdctl --namespace=nerdctl-test ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c9c847257348 myregistry.domain.com:5001/stargz-containers/alpine:3.13-org "/bin/grep shm /proc…" Less than...

Syx5290

cnitool example: ping doesn't work

1

I'm trying the [cnitool example](https://www.cni.dev/docs/cnitool/#example-invocation) and it works up until testing the created network. ping says one package send, but none received. OS: openSUSE tumbleweed cnitool: latest version That's what...

hobyte

Relation between Kubernetes and CNI

2

https://www.cni.dev/docs/#who-is-using-cni says that both Kubernetes and CRI-O use CNI. https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#installation says that Kubernetes loads a Container Runtime, like cri-o, and the latter utilizes CNI. For me the second citation means...

dilyanpalauzov

Defaults for `name` and `disableCheck` in configuration files

4

https://www.cni.dev/docs/spec/#configuration-format describes the /etc/cni/net.d/ configuration files. Please write down, whether the `"name"` parameter is mandatory and what happens, if it is optional and missing. https://github.com/cri-o/cri-o/blob/main/contrib/cni/99-loopback.conf is an example without `"name":`....

dilyanpalauzov

Many discrepancies between the SPEC and the code

6

For context, I've been playing around with implementing a CNI plugin in Rust. My assumption was that the spec should be sufficient to do this, but in practice, there is...

dave-tucker

Add definition for attachment

1

I noticed we used attachment a few times in the spec and wanted to add it terminology. At a minimum if this is not added we should correct three to...

MikeZappa87

2.0: Consider daemonization

13

## Background The exec-based API can be awkward for a few reasons: - Many plugins need a daemon anyways - Writing binaries to disk is a security risk - Executing...

squeed

fix 714-plugin add netns validation reinforcement

9

fix-714: https://github.com/containernetworking/plugins/issues/714

Poor12

2.0: Protobuf / gRPC: how to pass network configuration to plugins?

1

Assuming we move forward with daemonization (#821), then we will have to write a protobuf schema for the CNI protocol. This tpresents a few awkward edges around network configuration. The...

squeed