Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

control plane on multiple clusters #967

Closed
matti opened this issue Jun 4, 2019 · 1 comment
Closed

control plane on multiple clusters #967

matti opened this issue Jun 4, 2019 · 1 comment
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@matti
Copy link

matti commented Jun 4, 2019

This might be an documentation issue - currently it's not clear if the control plane can be hosted in multiple clusters or not - documentation should state that it is not supported.

If so, then can the control plane be moved to another cluster? The docs should also cover that.

/kind docs

@marun marun added the kind/support Categorizes issue or PR as a support question. label Jun 5, 2019
@marun
Copy link
Contributor

marun commented Jun 5, 2019

No, the control plane cannot be hosted on multiple clusters. KubeFed provides Kubernetes API types and controllers that run on a single cluster, just like any other Kube service. Running simultaneously on multiple clusters would require exposing a non-Kube API backed by a distributed data store (and probably not etcd depending on latency between clusters).

Since #636 has already been filed to cover the topic of disaster recovery (which encompasses the topic of migration of the control plane), I think this issue can likely be closed as a duplicate.

@marun marun closed this as completed Jun 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

2 participants