Skip to content

Distinguish duplicate kinds #1740

@adityathebe

Description

@adityathebe

We have multiple Kubernetes resources with the same kind but different API versions, which creates naming conflicts. To resolve this, we need to use prefixed names for custom resources that disambiguate them from core resources.

Examples of Conflicts

Core/Generated Resource Custom Resource Proposed Name
v1:Node longhorn.io/v1beta2:Node LonghornNode
config-db:Cluster postgresql.cnpg.io/v1:Cluster CnpgCluster

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions