github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-27 21:47:07 +00:00
Code Issues Projects Releases Wiki Activity

Remove outdated documented Mesos issue that service ports must be named

Browse Source 
The described behavior cannot be reproduced in current master anymore.

Compare mesosphere/kubernetes-mesos#322
This commit is contained in:
Dr. Stefan Schimanski 2015-08-13 00:44:27 +02:00
parent 22fc45c98a
commit f8dd75091d
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
contrib/mesos/docs/issues.md
View File

@ -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. 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. 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: To disable the work-around and revert to vanilla Kubernetes service endpoint termination: