whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs revision

Browse Source 
Signed-off-by: Aldo Culquicondor <acondor@google.com>
This commit is contained in:
Aldo Culquicondor
2020-07-13 14:30:00 -04:00
parent e02160c63c
commit 91b83cf906
2 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md
+6 -5
View File
@@ -228,7 +228,8 @@ using default constraints for `PodTopologySpread`.
{{< feature-state for_k8s_version="v1.19" state="alpha" >}} {{< feature-state for_k8s_version="v1.19" state="alpha" >}}
When the feature gate `DefaultPodTopologySpread` is enabled, When you enable the `DefaultPodTopologySpread` feature gate, the
legacy `SelectorSpread` plugin is disabled.
kube-scheduler uses the following default topology constraints for the kube-scheduler uses the following default topology constraints for the
`PodTopologySpread` plugin configuration: `PodTopologySpread` plugin configuration:
@@ -247,11 +248,11 @@ is disabled.
{{< note >}} {{< note >}}
If your nodes are not expected to have **both** `kubernetes.io/hostname` and If your nodes are not expected to have **both** `kubernetes.io/hostname` and
`topology.kubernetes.io/zone` labels set, you should define your own constraints `topology.kubernetes.io/zone` labels set, define your own constraints
instead of using the Kubernetes default. instead of using the Kubernetes defaults.
The `PodTopologySpread` plugin ignores from scoring the nodes that don't have The `PodTopologySpread` plugin does not score the nodes that don't have
both topologies. the topology keys specified in the spreading constraints.
{{< /note >}} {{< /note >}}
## Comparison with PodAffinity/PodAntiAffinity ## Comparison with PodAffinity/PodAntiAffinity
content/en/docs/reference/command-line-tools-reference/feature-gates.md
+3
View File
@@ -80,6 +80,7 @@ different Kubernetes components.
| `CustomCPUCFSQuotaPeriod` | `false` | Alpha | 1.12 | | | `CustomCPUCFSQuotaPeriod` | `false` | Alpha | 1.12 | |
| `CustomResourceDefaulting` | `false` | Alpha| 1.15 | 1.15 | | `CustomResourceDefaulting` | `false` | Alpha| 1.15 | 1.15 |
| `CustomResourceDefaulting` | `true` | Beta | 1.16 | | | `CustomResourceDefaulting` | `true` | Beta | 1.16 | |
| `DefaultPodTopologySpread` | `false` | Alpha | 1.19 | |
| `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 | | `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 |
| `DevicePlugins` | `true` | Beta | 1.10 | | | `DevicePlugins` | `true` | Beta | 1.10 | |
| `DryRun` | `false` | Alpha | 1.12 | 1.12 | | `DryRun` | `false` | Alpha | 1.12 | 1.12 |
@@ -404,6 +405,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
troubleshoot a running Pod. troubleshoot a running Pod.
- `DevicePlugins`: Enable the [device-plugins](/docs/concepts/cluster-administration/device-plugins/) - `DevicePlugins`: Enable the [device-plugins](/docs/concepts/cluster-administration/device-plugins/)
based resource provisioning on nodes. based resource provisioning on nodes.
- `DefaultPodTopologySpread`: Enables the use of `PodTopologySpread` scheduling plugin to do
[default spreading](/docs/concepts/workloads/pods/pod/pod-topology-spread-constraints/#internal-default-constraints).
- `DryRun`: Enable server-side [dry run](/docs/reference/using-api/api-concepts/#dry-run) requests - `DryRun`: Enable server-side [dry run](/docs/reference/using-api/api-concepts/#dry-run) requests
so that validation, merging, and mutation can be tested without committing. so that validation, merging, and mutation can be tested without committing.
- `DynamicAuditing`: Enable [dynamic auditing](/docs/tasks/debug-application-cluster/audit/#dynamic-backend) - `DynamicAuditing`: Enable [dynamic auditing](/docs/tasks/debug-application-cluster/audit/#dynamic-backend)