mirror of
https://github.com/optim-enterprises-bv/kubernetes.git
synced 2025-11-02 03:08:15 +00:00
Merge pull request #26956 from joe2far/fix-typos
Automatic merge from submit-queue Fixed several typos
This commit is contained in:
@@ -28,7 +28,7 @@ This project combines concepts and technologies from two already-complex project
|
||||
|
||||
To get up and running with Kubernetes-Mesos, follow:
|
||||
|
||||
- the [Getting started guide](../../docs/getting-started-guides/mesos.md) to launch a Kuberneters-Mesos cluster,
|
||||
- the [Getting started guide](../../docs/getting-started-guides/mesos.md) to launch a Kubernetes-Mesos cluster,
|
||||
- the [Kubernetes-Mesos Scheduler Guide](./docs/scheduler.md) for topics concerning the custom scheduler used in this distribution.
|
||||
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ Setting either of these flags to non-zero values may impact connection tracking
|
||||
In order for pods (replicated, or otherwise) to be scheduled on the cluster, it is strongly recommended that:
|
||||
* `pod.spec.containers[x].ports[y].hostPort` be left unspecified (or zero), or else;
|
||||
* `pod.spec.containers[x].ports[y].hostPort` exists in the range of `ports` resources declared on Mesos slaves
|
||||
- double-check the resource declaraions for your Mesos slaves, the default for `ports` is typically `[31000-32000]`
|
||||
- double-check the resource declarations for your Mesos slaves, the default for `ports` is typically `[31000-32000]`
|
||||
|
||||
Mesos slave host `ports` are resources that are managed by the Mesos resource/offers ecosystem; slave host ports are consumed by launched tasks.
|
||||
Kubernetes pod container specifications identify two types of ports, "container ports" and "host ports":
|
||||
|
||||
@@ -72,7 +72,7 @@ type Registry interface {
|
||||
}
|
||||
|
||||
// callback that is invoked during a walk through a series of live offers,
|
||||
// returning with stop=true (or err != nil) if the walk should stop permaturely.
|
||||
// returning with stop=true (or err != nil) if the walk should stop prematurely.
|
||||
type Walker func(offer Perishable) (stop bool, err error)
|
||||
|
||||
type RegistryConfig struct {
|
||||
|
||||
@@ -116,7 +116,7 @@ func (a AllOrNothingProcurement) Procure(t *T, n *api.Node, ps *ProcureState) er
|
||||
}
|
||||
|
||||
// NewNodeProcurement returns a Procurement that checks whether the given pod task and offer
|
||||
// have valid node informations available and wehther the pod spec node selector matches
|
||||
// have valid node informations available and whether the pod spec node selector matches
|
||||
// the pod labels.
|
||||
// If the check is successful the slave ID and assigned slave is set in the given Spec.
|
||||
func NewNodeProcurement() Procurement {
|
||||
|
||||
Reference in New Issue
Block a user