Fix some errors
Jihoon Seo
parent
3599c03929
commit
c76c3784aa
|
|
@ -64,7 +64,7 @@ The Kubernetes community has written a [detailed blog post about deprecation](ht
|
|||
|
||||
A longstanding bug regarding exec probe timeouts that may impact existing pod definitions has been fixed. Prior to this fix, the field `timeoutSeconds` was not respected for exec probes. Instead, probes would run indefinitely, even past their configured deadline, until a result was returned. With this change, the default value of `1 second` will be applied if a value is not specified and existing pod definitions may no longer be sufficient if a probe takes longer than one second. A feature gate, called `ExecProbeTimeout`, has been added with this fix that enables cluster operators to revert to the previous behavior, but this will be locked and removed in subsequent releases. In order to revert to the previous behavior, cluster operators should set this feature gate to `false`.
|
||||
|
||||
Please review the updated documentation regarding [configuring probes](docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) for more details.
|
||||
Please review the updated documentation regarding [configuring probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) for more details.
|
||||
|
||||
## Other Updates
|
||||
|
||||
|
|
|
|||
|
|
@ -192,7 +192,7 @@ parallelism, for a variety of reasons:
|
|||
{{< note >}}
|
||||
To be able to create Indexed Jobs, make sure to enable the `IndexedJob`
|
||||
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
|
||||
on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/).
|
||||
{{< /note >}}
|
||||
|
||||
|
|
@ -412,7 +412,7 @@ Here, `W` is the number of work items.
|
|||
{{< note >}}
|
||||
Suspending Jobs is available in Kubernetes versions 1.21 and above. You must
|
||||
enable the `SuspendJob` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
|
||||
on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/)
|
||||
in order to use this feature.
|
||||
{{< /note >}}
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ configuration, or reinstall it using automation.
|
|||
|
||||
### Migrating to the `systemd` driver in kubeadm managed clusters
|
||||
|
||||
Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver)
|
||||
Follow this [Migration guide](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/)
|
||||
if you wish to migrate to the `systemd` cgroup driver in existing kubeadm managed clusters.
|
||||
|
||||
## Container runtimes
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ In this document, when we talk about Windows containers we mean Windows containe
|
|||
Refer to the following table for Windows operating system support in Kubernetes. A single heterogeneous Kubernetes cluster can have both Windows and Linux worker nodes. Windows containers have to be scheduled on Windows nodes and Linux containers on Linux nodes.
|
||||
|
||||
| Kubernetes version | Windows Server LTSC releases | Windows Server SAC releases |
|
||||
| --- | --- | --- | --- |
|
||||
| --- | --- | --- |
|
||||
| *Kubernetes v1.17* | Windows Server 2019 | Windows Server ver 1809 |
|
||||
| *Kubernetes v1.18* | Windows Server 2019 | Windows Server ver 1809, Windows Server ver 1903, Windows Server ver 1909 |
|
||||
| *Kubernetes v1.19* | Windows Server 2019 | Windows Server ver 1909, Windows Server ver 2004 |
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ The following prerequisite is needed in order to enable topology aware hints:
|
|||
## Enable Topology Aware Hints
|
||||
|
||||
To enable service topology hints, enable the `TopologyAwareHints` [feature
|
||||
gate](docs/reference/command-line-tools-reference/feature-gates/) for the
|
||||
gate](/docs/reference/command-line-tools-reference/feature-gates/) for the
|
||||
kube-apiserver, kube-controller-manager, and kube-proxy:
|
||||
|
||||
```
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ kubeadm init --config kubeadm-config.yaml
|
|||
|
||||
{{< note >}}
|
||||
Kubeadm uses the same `KubeletConfiguration` for all nodes in the cluster.
|
||||
The `KubeletConfiguration` is stored in a [ConfigMap](docs/concepts/configuration/configmap)
|
||||
The `KubeletConfiguration` is stored in a [ConfigMap](/docs/concepts/configuration/configmap)
|
||||
object under the `kube-system` namespace.
|
||||
|
||||
Executing the sub commands `init`, `join` and `upgrade` would result in kubeadm
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ non-parallel, use of [Job](/docs/concepts/workloads/controllers/job/).
|
|||
|
||||
To be able to create Indexed Jobs, make sure to enable the `IndexedJob`
|
||||
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
|
||||
on the [API server](docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
|
||||
and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/).
|
||||
|
||||
<!-- steps -->
|
||||
|
|
|
|||
Loading…
Reference in New Issue