Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
We decided to get rid of boundPods. Removing this check is a prerequisite for that. This check had some value before we had IP-per-Pod. However, AIUI, use of HostPort is strongly discouraged in Kubernetes. It still exists as part of a Pod spec because of ContainerVM, where it is used. But, this change does not affect ContainerVM, where there is no master. If someone did create pods with HostPort using kubernetes, the following would happen: - The scheduler would try not to put two conflicting pods on the same machine (pkg/scheduler/predicates.go : PodFitsPorts() ) - I'm not sure if it is currently possible for a race to occur where the PodFitsPorts check were bypassed. Maybe it could happen. - If the kubelet was sent conflicting pods, it would detect them in ( pkg/kubelet/kubelet.go : filterHostPortConflicts() ). It would arbitrarily pick one pod to run and another to ignore. - If all of the above happened and the user filed and issue on github, we might figure out that the user used HostPort and tell the user to stop. TODO: - e2e test - Several of the demos in examples/ use hostPort. Change them to not specify hostPort and have a service instead.
- Loading branch information