From 85bbe9f338500bc52b0ac49094b066346fcf6c2c Mon Sep 17 00:00:00 2001 From: Joe Betz Date: Tue, 21 Nov 2023 17:12:41 -0800 Subject: [PATCH] Request to be promoted to PRR approver Shadow contributions: - 1.27 shadow reviews: 6 - 1.28 shadow reviews: 9 - 1.29 - did not shadow due to time constraints with new SIG API Machinery TL role Planned contributions: - 1.30+ contribute to PRR, able to review roughly 12 KEPs per release. I am happy to PRR more than 12 so long as they are SIG API Machinery KEPs, since I'll be reviewing those anyway.. Shadow reviewer promotion criteria: Transitions from new to alpha - https://github.com/kubernetes/enhancements/issues/3983 - https://github.com/kubernetes/enhancements/issues/3751 Transitions from alpha to beta - https://github.com/kubernetes/enhancements/issues/3107 - https://github.com/kubernetes/enhancements/issues/2485 Transitions from beta to GA - https://github.com/kubernetes/enhancements/issues/2268 Three enhancements that require coordination between multiple components. - https://github.com/kubernetes/enhancements/issues/3751 - https://github.com/kubernetes/enhancements/issues/2485 - https://github.com/kubernetes/enhancements/issues/3107 Three enhancements that require version skew consideration (both HA and component skew): does behavior fail safely and eventually reconcile. - https://github.com/kubernetes/enhancements/issues/2268 (component skew) - https://github.com/kubernetes/enhancements/issues/2485 (component skew) - https://github.com/kubernetes/enhancements/issues/3751 (HA skew - feature gated fields, component skew) https://github.com/kubernetes/enhancements/issues/2268 (HA skew of controller considered) Three enhancements that are outside your primary domain. - https://github.com/kubernetes/enhancements/issues/3983 (SIG Node) - https://github.com/kubernetes/enhancements/issues/3751 (SIG Storage) - https://github.com/kubernetes/enhancements/issues/2268 (SIG Node) - https://github.com/kubernetes/enhancements/issues/3107 (SIG Storage) Examples where the feature requires considering the case of administering thousands of clusters. This comes up frequently for host-based features in storage, node, or networking. - Yes. E.g. https://github.com/kubernetes/enhancements/issues/2268 (ability to analyze cluster in aggregate considered, rescheduling considered) Examples where the feature requires considering the case of very large clusters. This is commonly covered by metrics. - Yes. E.g. https://github.com/kubernetes/enhancements/issues/3751 (new API call, volume of calls considered) --- OWNERS_ALIASES | 1 + 1 file changed, 1 insertion(+) diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES index 19be8ade409..7e30e12ab72 100644 --- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -209,6 +209,7 @@ aliases: - johnbelamaric - deads2k - wojtek-t + - jpbetz prod-readiness-approvers-emeritus: - ehashman provider-aws: