From 60fc7bde7327c5fd41c54f96c9b85b234a0890b2 Mon Sep 17 00:00:00 2001
From: Gabriel Miretti <gmiretti@users.noreply.github.com>
Date: Tue, 24 Oct 2017 21:08:37 -0300
Subject: [PATCH] Using Helm in Openshift Kubernetes distribution

---
 docs/kubernetes_distros.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/kubernetes_distros.md b/docs/kubernetes_distros.md
index 7b5382893..620ef72ac 100644
--- a/docs/kubernetes_distros.md
+++ b/docs/kubernetes_distros.md
@@ -35,3 +35,7 @@ or create a `~/.kube/config`.
 ## 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 more read the [Kubelet Wrapper](https://coreos.com/kubernetes/docs/latest/kubelet-wrapper.html) docs.
+
+## Openshift
+
+Helm works straightforward on OpenShift Online, OpenShift Dedicated, OpenShift Container Platform (version >= 3.6) or OpenShift Origin (version >= 3.6). To learn more read [this blog](https://blog.openshift.com/getting-started-helm-openshift/) post.
-- 
GitLab