From edbc56175904b990c657437e841ccebf38fc7516 Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Fri, 30 Dec 2016 19:05:25 -0800 Subject: [PATCH] docs: kubernetes_distros: complete note about socat on Container Linux This fixes two things: 1) CoreOS Linux is now Container Linux https://coreos.com/blog/tectonic-self-driving.html#coreos-linux-is-now-container-linux 2) Provide more technical details on what is going on for users trying to debug and understand --- docs/kubernetes_distros.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/kubernetes_distros.md b/docs/kubernetes_distros.md index ed6cbf208..5c320fd34 100644 --- a/docs/kubernetes_distros.md +++ b/docs/kubernetes_distros.md @@ -32,10 +32,6 @@ distributions: Some versions of Helm (v2.0.0-beta2) require you to `export KUBECONFIG=/etc/kubernetes/admin.conf` or create a `~/.kube/config`. -## CoreOS - -Some versions of CoreOS's Kubernetes do not ship with `socat`, which is what -the Kubernetes API server uses to create tunnels. This will prevent Helm from -being able to tunnel to Tiller. - +## Container Linux by CoreOS +Helm requires that kubelet have access to a copy of the `socat` program to proxy connections to the Tiller API. On Container Linux the Kubelet runs inside of a [hyperkube](https://github.com/kubernetes/kubernetes/tree/master/cluster/images/hyperkube) container image that has socat. So, even though Container Linux doesn't ship `socat` the container filesystem running kubelet does have socat. To learn move read the [Kubelet Wrapper](https://coreos.com/kubernetes/docs/latest/kubelet-wrapper.html) docs.