-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Description
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 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels