Mo Khan
Mo Khan
/assign @andrewsykim
@rhockenbury thanks! Note that this is going `beta` in v1.26, not `alpha`.
We are currently only planning to use this repo to hold GitHub actions workflows to automate our project boards. Does that count as a sub project?
@mrbobbytables okay this PR is basically correct then. Should we add a description for the section like "Tooling to automate the SIG Auth project boards" ?
Why is this annotation based instead of a proper (alpha feature gated) field on the pod? What value does starting off as an annotation provide?
> The idea here is to not introduce a new api change before we move to beta... The annotation is a new API, just a harder to discover and reason...
> One nice thing about an annotation is as a webhook-injecting-sidecar implementor, I can just put it on all pods and if the cluster supports it - great. With a...
> We are not against api fields, seeing the issues sig-node faces when a core code is changed we decided to use annotation This sounds like an unrelated systemic problem?...
The code is [here](https://github.com/kubernetes/kubernetes/blob/1cbda2493d2744af0d0e52b008976af0fc1d3a5e/staging/src/k8s.io/kubectl/pkg/describe/describe.go#L3450-L3505) in case anyone wants to take a look.