Skip to content
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

Closed
podollb opened this issue Feb 20, 2017 · 26 comments
Closed

Support federated k8s cluster #1998

podollb opened this issue Feb 20, 2017 · 26 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@podollb
Copy link

podollb commented Feb 20, 2017

It seems that helm is unable to work with k8s federated clusters. Is getting that working on the roadmap?

@rcarlson8974
Copy link

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.

@technosophos
Copy link
Member

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.

@technosophos
Copy link
Member

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.

@rcarlson8974
Copy link

👍 👍 👍 👍 👍 👍 👍 👍 👍 👍

@podollb
Copy link
Author

podollb commented Feb 24, 2017

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).

@iamzhout
Copy link
Contributor

wanted +1 👍

@acts-human
Copy link

+1 👍

@unguiculus
Copy link
Member

👍

@0megam
Copy link

0megam commented Mar 7, 2017

👍

4 similar comments
@sethew
Copy link

sethew commented Mar 8, 2017

👍

@nilsher
Copy link

nilsher commented Mar 9, 2017

👍

@szibis
Copy link
Contributor

szibis commented Mar 9, 2017

👍

@nagas
Copy link

nagas commented Mar 9, 2017

👍

@technosophos
Copy link
Member

That's enough evidence to convince me. ;-)

@technosophos technosophos added this to the 2.4.0-Triage milestone Mar 15, 2017
@technosophos technosophos added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed support labels Mar 15, 2017
@v1k0d3n
Copy link
Contributor

v1k0d3n commented Mar 16, 2017

big huge 👍 from us @technosophos

@rimusz
Copy link
Contributor

rimusz commented Mar 16, 2017

👍

@bobhenkel
Copy link

bobhenkel commented Mar 28, 2017

👍 👍
The future is going to have a lot of federated clusters, support is really needed for this.

@rcarlson8974
Copy link

@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....

@bacongobbler
Copy link
Member

bacongobbler commented Oct 31, 2017

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.

@naveensrinivasan
Copy link

@technosophos Any update on this?

@v1k0d3n
Copy link
Contributor

v1k0d3n commented Feb 19, 2018

huge 👍👍 from this guy... :)

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@v1k0d3n
Copy link
Contributor

v1k0d3n commented May 21, 2018

@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.

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@danehans
Copy link

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?

@bacongobbler
Copy link
Member

closing as stale. Please feel free to comment here if you're working on federation support. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests