Tim Hockin

Is this one going anywhere for 1.25?

For the record: it sounds like we're waiting for runtimes to implement, so no advancement for 1.23, right?

We did not queue this up for 1.24, so I will tag for 25 and we can re-evaluate then

@gjkim42 Are we trying to push this to Beta for 1.26?

All we need by deadline is any edits to the KEP itself, right?

I'll have to think about this. In truth, I have very little desire to support go 1.16 or earlier. That's 18 months old.

I think it is long-term valuable but not near-term

sippy is the only old-style cert remaining, except for the self-signed we use in k8s-io-canary (which maybe can just go away?)

Shall we discuss the idea sometime and you can either volunteer yourself or write enough that we can solicit other volunteers? On Mon, Dec 16, 2019 at 3:00 PM Christoph...

For what it's worth, I'd *love* to see this be more formalized. But I agree with Aaron - it's not as simple as getting people to sign up. This is...