Gabe Rosenhouse

We're veering away from CNI and into runtime design questions, but in short, yes. I wouldn't call it "partially deleted state" though. I would describe it as "containers that shouldn't...

What kind of version would you want to be reported? The CNI spec version used by the golang library inside `cnitool`? Or the version of the GitHub release? The reason...

@sboeuf Could you share a bit more about your use case? Are you asking for the route structure in the [specification](https://github.com/containernetworking/cni/blob/master/SPEC.md#result) to change as well, or just the Go library?

@sboeuf I don't think we're interested in adding fields to the CNI Go library that aren't part of the CNI spec. Perhaps you can use a [structure embedding](https://golang.org/doc/effective_go.html#embedding) to address...

@containernetworking/cni-maintainers I recall there being some prior discussion of adding a source field to `routes` in the CNI spec result, but couldn't find it....

Crazy idea: What if, instead of making a spec change for every X, we had a result field that was analogous to the `args` on the config struct. In other...

@FlorianOtel is your issue addressed here? If so, please close. Thank you!

Thanks for all your work to take over and improve metacontroller. This feature (standalone) is really appealing to me, but I wanted to point out two potential issues with the...

cc @adobley @KauzClay @ameowlia @shalako who have been thinking about enhancements to ASGs

hey @jaytaylor I'm looking at the V4 implementation in `satori/go.uuid` and the one here. I'm not seeing any meaningful differences. Could you explain what about the V4 code path is...