-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support federated k8s cluster #1998
Comments
This is our #1 issue right now. To get HA, we need to be in multiple regions and zones. To deploy once, we need Federated clusters. Without this getting implemented, we have to do something kludgy like running a helm command per cluster, which is less than ideal or dropping down to kubectl which also has limitations. I would love to see this added to the road map. |
We would love to add this feature. We talked about it during the last KubeCon, but honestly we need some help. Tiller can talk to exactly one Kubernetes API server right now. If that API server can make the federation transparent, Helm could probably work. I'd need to look at the docs, but if the control plane provides a Kubernetes API server, it might be possible to deploy Tiller into the control plane and point it at that API server. But, again, I don't know enough about the functioning of a federation to be sure about this. Would love to talk about this more, and begin identifying the details. |
I'm trying to gauge interest in this feature. Please weigh in here (even if it's just a 👍 ) so that I can figure out how important this is to people. |
👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 |
Agree. It's pretty important IMHO, especially now that people are starting to move to federated k8s deployments (so it's a fork in the road, to continue to use helm, with no support to deploy to a federated k8s with helm). |
wanted +1 👍 |
+1 👍 |
👍 |
👍 |
4 similar comments
👍 |
👍 |
👍 |
👍 |
That's enough evidence to convince me. ;-) |
big huge 👍 from us @technosophos |
👍 |
👍 👍 |
@technosophos ballpark ETA on when something (even beta) might be ready? We are going live in a couple weeks and if there was a chance something would be ready by then, it would change some of our sprint planning, etc.... |
no ballpark ETA on this. There is an experimental backend for tiller at https://github.com/kubernetes-helm/rudder-federation which @nebril is working on, but there are no plans on adding this to the roadmap any time soon. Please feel free to give that project a shot, though! I know your comment was from March, but from what I've seen, federation support was just pulled out of kubernetes core into https://github.com/kubernetes/federation so I'm not sure how far out federation support will be considered stable at this point. It's November (tomorrow) and kubernetes federation support is still very much in an alpha state. I wouldn't consider going live with federation support if you're going to be running this in production. |
@technosophos Any update on this? |
huge 👍👍 from this guy... :) |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@technosophos, this is a pretty old issue but maybe it could be retitled for the federation-v2 model? most everyone is well aware of this work already, but for those who aren't, the prototype work can be found at this link. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
federation-v2 appears to be the future of Kubernetes Federation. I understand v2 is not production ready, but should #2539 target this version instead of v1? |
closing as stale. Please feel free to comment here if you're working on federation support. Thanks! |
It seems that helm is unable to work with k8s federated clusters. Is getting that working on the roadmap?
The text was updated successfully, but these errors were encountered: