Request for approval: new k8s.io/webhookauth staging repo

[Benjamin Petersen]

Greetings!

For KEP-6060 (API Server Authentication to Webhooks) we'd like a new staging repo where we provide a small library to make it very easy for webhook authors to support this feature.

1. New staging repo for the sig-auth subproject: k8s.io/webhookauth
2. PR-140665 represents the code we expect to live in this new package
3. It must be a staging repo to make it easy to use as a dependency for webhooks
4. Issue created for this request: kubernetes/org 6505

Thanks!

~Ben

[Antonio Ojea]

I'd like to provide some architectural feedback that is worth considering in these cases. Because staging repos are part of the kubernetes/kubernetes core repository, any code placed there is subject to the exact same strict policies that govern the core repo. This includes our rules around cherry-picking, release cycles, and how breaking changes are handled.

Depending on your long-term goals for this library, you should consider the following:

- If the goal is to offer a stable, easily consumable library: It would be much better to handle this out-of-tree (e.g., as a standalone repository). This allows the library to maintain its own independent release cadence, semantic versioning, and stability guarantees without being bound to the Kubernetes core release cycle.

- If the goal is to offer a tightly coupled wrapper: Staging could make sense, but only if end-users are fully prepared to deal with breaking changes and the necessity of bumping their versions in lockstep with Kubernetes core releases.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/2cc48550-00ef-49f4-8c13-9c71997e4cc4n%40googlegroups.com.

[Peter Engelbert]

To keep discussion centralized, I've responded to this and one other question here:

https://github.com/kubernetes/org/issues/6505#issuecomment-5048730738