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
Proposal: Upstream Kubernetes-Mesos framework #6676
Comments
/cc @zmerlynn @alex-mohr |
@jdef Re: wish list - most likely post 1.0 at this point. |
Could we add the Mesos tag to this issue? |
Sure. |
Thanks for the writeup. My main question is about "no static pod support." We are planning to use static pods for a bunch of things. On the nodes for the monitoring/logging stack (cAdvisor, etc.) and on the master for running the master components (which will run in containers). Can you explain why static pods won't work? Independent of Mesos, we need a way to make static pods work with dynamically-added nodes anyway since we want to support dynamically growing clusters, so I don't think the fact that the Mesos scheduler dynamically adds and removes nodes should prevent static pods from working (once we have all of this working). cc/ @dchen1107 |
My initial thinking was based on the presumption that static pods are One way to do this would be to specify the static pod configuration (as a On Sat, Apr 11, 2015 at 1:49 AM, David Oppenheimer <notifications@github.com
James DeFelice |
Yeah, I can't think of any reason why we'd need the static pods to be running on nodes that aren't part of the k8s cluster, i.e. don't have kubelet running. As for your proposal, I think we should try to get the static pods running using whatever mechanism is closest to how we do it in native Kubernetes. TBH I don't remember how this will work (maybe using file source, in which case it would be somewhat close to what you are proposing). Hopefully @dchen1107 or @yujuhong can comment. One thing I'm wondering about your question, though, is why is the resource accounting aspect new? The things we're running as static pods are things that already run on the node today, just outside of pods. So the fact that the amount of available resources needs to take them into account doesn't change when they move into static pods. |
From what I remember of the code, I think that the file source can be used The resource accounting is important because even though these are static On Sun, Apr 12, 2015 at 3:07 PM, David Oppenheimer <notifications@github.com
James DeFelice |
@davidopp the Kubelet has a directory it watches for static pod configurations and starts any present there. The plan is to drop the config files for the desired pods there. It seems that the resource accounting issue is mainly that the information is coming from Mesos and not Kubernetes? In theory Kubernetes could account for its own overhead on the node without over-subscribing the node (it does not today). |
Not sure about cadvisor (since it now appears to be embedded within the On Mon, Apr 13, 2015 at 4:44 PM, Timothy St. Clair <notifications@github.com
James DeFelice |
Static pods are accounted in the master via the "mirror pods" feature that was recently added. See #4090 kubelet, docker, and kube-proxy don't run at pods at all, so their resources aren't accounted at all. I'm not sure which pods run as static pods currently vs. regular pods. The candidates are fluentd, elasticsearch, kibana, kube-dns, heapster, influx-grafana. I think it may only be fluentd (as static pods). I'll find out. |
@yujuhong says that fluentd-to-elasticsearch-kubernetes (image name fluentd-elasticsearch) is the only thing running as a static pod on the nodes (i.e. not master) right now. |
Thanks for the info. It sounds like static pod support the only blocker. Can I assume that we have a green light for submitting a PR for the phase1 stuff once static pod support is in place? |
👍 I'm looking forward to having this PR submitted. |
|
@jdef I vote for |
+1 to contrib, pretty standard. |
@jdef any update here? |
getting closer to having things ready to upstream. team has been working on On Mon, May 4, 2015 at 4:03 PM, Timothy St. Clair notifications@github.com
James DeFelice |
Upstreaming is effectively complete. TODO:
|
🎉 |
Overview
Goals
Dependencies / Assumptions
Core Integration
Build & Deploy
Framework
Cluster Provider
Salt
Wish List
cc @bgrant0607 @davidopp @guenter @timothysc @ConnorDoyle
The text was updated successfully, but these errors were encountered: