Skip to content

Move APIs into a central location #12203

Closed
@sbueringer

Description

@sbueringer

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:

  • Why?
    • Easier to find our APIs when they are in a central location. Currently that's a non-trivial exercise for our users
    • It enables us to introduce a separate api go module (this is not part of the current issue though)
  • Why now? We are currently introducing v1beta2, folks will have to change their import paths anyway
  • This does not include CAPD as it is not intended for production usage

The new structure would look roughly like this:

Image

Additional tasks:

  • Also align internal/apis folder

Metadata

Metadata

Assignees

Labels

kind/api-changeCategorizes 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.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions