Bryan Boreham

> require plugins to register themeslves with the container orchestrator Can we learn from orchestrator plugin interfaces like CRI and CSI?

> What does a gRPC interface provide that can't be achieved by invoking plugins as containers? > Is the mechanism of exec'ing a binary in any way limiting? ie if...

> plugins implemented in languages other than go [...] incompatible with gRPC gRPC supports [lots of languages](https://grpc.io/docs/languages/), including C which many more can call.

Good spot. I don't see any alternative to effectively defaulting `IgnoreUnknown` to `true` in a chained configuration.

Is `Pdeathsig` another way to achieve this?

I'd like to know why it is called `capabilityArgs`. Does it relate to "capabilities" described in CONVENTIONS.md? And why "args" when it is part of the result?

> Should the cniVersion of the error payload also match the input's cniVersion? The [spec](https://github.com/containernetworking/cni/blob/8b25a7bf9e4a70b306074b704aaf39910d6d1dd8/SPEC.md#error) now says "cniVersion: The same value as provided by the configuration", so yes. > what...

Given current implementation in Kubernetes, having the plugin send an error to stderr will make it visible (in kubelet logs). This now seems a bit below the level of the...

You're correct, the spec should be changed. The namespace was made optional to cope with the case that the container has gone away (so there is no namespace) but the...

The current idea is that the cluster administrator knows what they want, and may get that by combining features from multiple plugins. It’s not aimed at vendors at all. Can...