controller-manager in k8sm:
- rename host_port_endpoints flag to host-port-endpoints
- host port mapping strategy in scheduler should be driven by host-port-endpoints flag
- added host-port-endpoints to known flags
- docs: scheduler should also be configured with host-port-endpoints
- task recovery: be explicit about excluding mirror pods
The scheduler documentation was updated to:
1. Reflect the `--mesos-framework-roles` and `--mesos-default-pod-roles`
configuration options.
2. Reflect pod roles configuration via annotations rather than labels.
3. The section describing more than two roles was modified to describe
only two roles because that is what is currently supported in Mesos.
- flag corrections
- split into general vs. DCOS known issues
- added lots of missing docs re: services, endpoints, upgrades,
scheduler
- clarified pod/ports section
- cross-referenced open github issues where applicable
Check to make sure there is not an alphanumeric character immeditely
before or after the 'flag'. It there is an alphanumeric character then
this is obviously not actually the flag we care about. For example if
the project declares a flag "valid-name" but the regex finds something
like "invalid_name" we should not match. Clearly this "invalid_name" is
not actually a wrong usage of the "valid-name" flag.
Before NodeName in the pod spec was used. Hence, pods with a fixed, pre-set
NodeName were never scheduled by the k8sm-scheduler, leading e.g. to a failing
e2e intra-pod test.
Fixesmesosphere/kubernetes-mesos#388