Aaron Prindle

> Missing charter.md to outline scope and exit criteria. Oof, my mistake thanks for pointing this out. I've updated the PR here to have the completed charter.md file now for...

> Also curious, is this a permanent problem space like Code Organization Subproject of SIG Arch, or a scoped effort that will conclude? If it's the former a SIG API...

@jbub I believe this was fixed in `v1.8.0` - can you confirm if this issue was fixed for you or if you are still encountering this? Thanks

/sig api-machinery /wg api-machinery

Thanks @lzung and @dipesh-rawat. The goal for the KEP currently is to get it merged before the enhancements freeze for 1.33. From the comments above I believe for this KEP,...

@hacktivist123 thanks for the information here! The KEP adds 2 feature gates which should be documented in the k/website repo. I have followed the steps posted ([link](https://kubernetes.io/docs/contribute/new-content/new-features/#open-a-placeholder-pr)) and submitted a...

@dipesh-rawat - thanks for the information here. I have submitted a PR to fix the issue with the Release Signoff Checklist: https://github.com/kubernetes/enhancements/pull/5171 The KEP itself was reviewed and approved by...

/milestone v1.34 /cc @jpbetz for the lead opt-in label

Yes, this would be targeting beta again for 1.34.

@rayandas Declarative Validation (KEP 5073) has no `stage` changes in v1.34. There is only additional work on the feature being done in v1.34 and expansion into one additional type is...