The conclusion is that this API (for obtaining the kubeconfig of a cluster of a logical cloud directly from dcm) is not implemented at all. rsync will get the kubeconfig from dcm, which is enough to get the logical resources installed in each cluster. However, a different kubeconfig needs to be created so that it can be handed to the owners of the logical clouds. This is why we need this specific kubeconfig API in dcm itself. A different task should be created in the future in order to implement a custom kubeconfig (with the right user, permissions, etc) per cluster in logical cloud. Closing story.