Skip to content

Creating a new API group is really hard #18762

Closed
@deads2k

Description

Creating a new API group is really hard. I'll keep this description up to date as I go through the pain.

  1. You have to know to add yourself to the import_known_versions.go files in multiple packages to get included.
  2. You have to manually update these files to get the generated output:
    1. hack/after-build/update-generated-conversions.sh
    2. hack/after-build/update-generated-deep-copies.sh
    3. hack/after-build/verify-generated-conversions.sh
    4. hack/after-build/verify-generated-deep-copies.sh
    5. hack/update-generated-swagger-docs.sh
  3. You have to manually create types.generated.go in every internal and external package to get codec-gen to work.
  4. You have to update pkg/api/registered/registered.go to be allowed to install your group.

That's just to get your types registered. Right now, there's no pluggable way to include custom RESTStorage into the API server for my new types.

@caesarxuchao @lavalamp @liggitt @smarterclayton
@kubernetes/rh-cluster-infra @kubernetes/goog-csi

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions