Dear SIG,
After 9 years of Kubernetes (and 10 at Google), I'm feeling quite burned out and I need to take a long break. So, unfortunately, I will be stepping down as API Machinery TL. Kubernetes has been the highlight of my career, so I'm reluctant to do this, but it is past time.
I propose that Joe Betz should take on the TL role. In addition to having deep etcd knowledge, he has added / led the addition of large pieces of functionality, such as the ApplyConfigurations client and CEL validations, and I'm confident he will be a great co-TL.
I think the process we should use is lazy consensus; if you have any concerns about this please reach out here, at tomorrow's SIG meeting, or if you prefer, directly contact myself (via slack), Fede, or David. We'll target 1-2 weeks for this.
(Aside: we haven't clearly documented the requirements for the TL role, we're aware of this, and Fede and I--mostly Fede--have been working on a "contributor ladder" doc, but it is a hard problem and far from finished. The SIG is extremely broad. I am confident that Joe is a good choice--probably the best--for this under any conceivable set of requirements.)
I am not going to completely disappear, but I am going to limit myself to just occasionally checking in on slack once in a while for at least a few months. I will spend time with my wife and 4 kids instead.
Daniel / lavalamp