From f8dd75091d1573e1ca08764033d5da36b358eb51 Mon Sep 17 00:00:00 2001 From: "Dr. Stefan Schimanski" Date: Thu, 13 Aug 2015 00:44:27 +0200 Subject: [PATCH] Remove outdated documented Mesos issue that service ports must be named The described behavior cannot be reproduced in current master anymore. Compare mesosphere/kubernetes-mesos#322 --- contrib/mesos/docs/issues.md | 1 - 1 file changed, 1 deletion(-) diff --git a/contrib/mesos/docs/issues.md b/contrib/mesos/docs/issues.md index 6ec400db1d0..facaa01c387 100644 --- a/contrib/mesos/docs/issues.md +++ b/contrib/mesos/docs/issues.md @@ -39,7 +39,6 @@ This is problematic when default Docker networking has been configured, such as The k8sm project has implemented a work-around: service endpoints are terminated at HostIP:HostPort, where the HostIP is the IP address of the Mesos slave and the HostPort is the host port declared in the pod container port specification. Host ports that are not defined, or else defined as zero, will automatically be assigned a (host) port resource from a resource offer. -When using the `controller-manager` provided by this project users should be sure to assign a `name` to each `service.spec.port` object, otherwise errors may reported in the endpoints controller manager regarding non-unique port values (#322). To disable the work-around and revert to vanilla Kubernetes service endpoint termination: