From 15a812a6366b6d942cbb43f04a6e1bd50561bdc8 Mon Sep 17 00:00:00 2001 From: Aaron Roydhouse Date: Tue, 2 Jan 2018 21:42:53 -0500 Subject: [PATCH] Update that fixed since Kubernetes 1.7.0 Update that fixed since Kubernetes 1.7.0 (as noted in the upstream issue) I've been testing with 1.8 and not see this problem there either. --- docs/troubleshooting/known-limitations.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/troubleshooting/known-limitations.md b/docs/troubleshooting/known-limitations.md index 113b89b1b..88682ab4a 100644 --- a/docs/troubleshooting/known-limitations.md +++ b/docs/troubleshooting/known-limitations.md @@ -1,6 +1,6 @@ # Known Limitations -## hostPort doesn't work +## hostPort doesn't work before Kubernetes 1.7.0 This is a known issue with Kubernetes while using CNI with no available workaround for kube-aws. `hostPort` does not work if `hostNetwork: false`. @@ -14,8 +14,10 @@ spec: name: nginx-ingress-lb ``` +This is fixed in Kubernetes 1.7.0 and later. + Relevant kube-aws issue: [does hostPort not work on kube-aws/CoreOS?](https://github.com/kubernetes-incubator/kube-aws/issues/91) See [the related upstream issue](https://github.com/kubernetes/kubernetes/issues/23920#issuecomment-254918942) for more information. -This limitation is also documented in [the official Kubernetes doc](http://kubernetes.io/docs/admin/network-plugins/#cni). \ No newline at end of file +This limitation is also documented in [the official Kubernetes doc](http://kubernetes.io/docs/admin/network-plugins/#cni).