-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Move APIs into a central location #12203
Copy link
Copy link
Closed
Labels
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APICategorizes issue or PR as related to adding, removing, or otherwise changing an APIpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Metadata
Metadata
Assignees
Labels
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APICategorizes issue or PR as related to adding, removing, or otherwise changing an APIpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Type
Fields
Give feedbackNo fields configured for issues without a type.
I think it would be great if our APIs would be in a central directory. Similar to https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/api
Notes:
apigo module (this is not part of the current issue though)The new structure would look roughly like this:
Additional tasks: