Support returning ip addresses with RunPodSandbox

[MikeZappa87]

This PR came out of a discussion with @mikebrow regarding if an alternative exists to adding PodSandboxStatus to NRI. He proposed adding ip addresses to the RunPodSandboxResponse.

#267

[squeed]

Should we add anything else? Interfaces? Routes?

[MikeZappa87]

I created an envelope msg that sets the stage for additional fields. Right now containerd has fields for the ip, additional ips but the fields you mention are part of the CNI result string. We could add them.

[mikebrow]

nod we can add the info map record for verbose status reporting later on.. with a follow-up

[MikeZappa87]

In the current we have a PodSandboxNetwork message which could provide typed fields instead? That might be preferable as we evolve the networking capabilities in NRI.

[mikebrow]

nod i presumed either map[key]=any json string... or typed fields if there's agreement on the definition

[MikeZappa87]

I think we should do both. The same convention in cri-api helps with extensibility and luckily for networking, a lot of fields have been well defined for some time. I think once this is merged, we can look to adding those fields.

[mikebrow]

err ^ best case

[mikebrow]

i like our pattern of supporting annotation meta for optional/experimental projects, and typed fields where we have solid ground

[MikeZappa87]

+1 for that as well. Perhaps we can just go ahead and add

[MikeZappa87]

nri/pkg/api/api.proto

Line 402 in 520641e

repeated string ips = 10;

We 'could' just return PodSandbox type as well and extend it with new fields?