Bug: ConfigSync installation applies ClusterRegistry CRD, is that necessary?

[johnbelamaric]

This causes problems because it registers the resource "clusters", which is shared, for example, with the Cluster API project. This can cause kubectl, etc. to be confused.

We may want to look over https://github.com/GoogleContainerTools/kpt-config-sync/tree/main/manifests and make sure we only apply the ones to the cluster that are actually needed at runtime by CS.

See also: nephio-project/nephio#327

[johnbelamaric]

To be clear - we are installing CS via config-management-operator.

[johnbelamaric]

@karlkfi

[karlkfi]

Is this still a problem, @johnbelamaric?

I don't see any ClusterRegistry resource manifests or CRDs in the repo.

I'm pretty sure ConfigSync excludes all objects in the /clusterregistry/ directory at the root of the repository. So if your Cluster object is there, to configure cluster labels, it shouldn't be applied.

For any other objects in your source repo you dont want applied you can add the config.kubernetes.io/local-config: "true" annotation.