WIP - Update SIG API Machinery annual-report-2024.md #8344
Conversation
k8s-ci-robot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fedebongio The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
cncf-cla: yes
|
/cc @jpbetz |
|
/cc @saschagrunert |
|
/hold |
k8s-ci-robot
added
the
do-not-merge/hold
fedebongio
changed the title
| - API Machinery area is very extense, here are some areas that could use extra help: | ||
| - Garbage Collection | ||
| - Resource Quota | ||
| - Server Side Apply |
There was a problem hiding this comment.
nit: would consider SSA as the most pressing. Could go to the top of the list.
There was a problem hiding this comment.
yes, good point! changed it
There was a problem hiding this comment.
Would it be useful to expand on what help these areas need? I'm trying to reason through why we would include Resource Quota and not controller infrastructure / clients.
Maybe expand Garbage Collection to something more general like Resource Lifecycle? We've got SVM and Namespace deletion ordering on our plate, and the Gateway API leads suggest that CRD lifecycle is a problem for their extensibility needs.
There was a problem hiding this comment.
Agree with you, I just put what came to my mind, but I was hoping to get more details or ideas from all of you.
ah, thanks... bad Google habits Co-authored-by: Dr. Stefan Schimanski <[email protected]>
re-shuffling to reflect order of priority
Which issue(s) this PR fixes:
Fixes # #8253
/sig api-machinery