How to handle the CRD conflict in mutiple cluster scenario about kcp HOT 4 CLOSED

As I had mentioned in the PR that integrated the CRD puller in the cluster controller, this is for now a very basic implementation of API resource import from external clusters, with no negociation at all in case of resource schema conflicts.

There should be some sort of schema negotiation when the same API resource is imported into a KCP logical cluster from several sources. We'll need to diff the various schemas and, when possible, finally use the least-common-denominator (LCD) of the various imported schemas. Some details of how this should be driven and managed are still to be defined and I'll let @smarterclayton complete / correct what I briefly answered here.

But to summarize: No the current behavior is not by design, and API resource import and negotiation is a key point of KCP that still needs to be fully specified & implemented.

from kcp.

For more details about CRD negotiation, see https://github.com/kcp-dev/kcp/blob/main/docs/investigations/logical-clusters.md#crd-virtualization-inheritance-and-normalization

from kcp.

Thanks @davidfestal
Expect to see the design details.

from kcp.

This should have been fixed by PR #116

from kcp.