Merge remote-tracking branch 'upstream/main' into dev-1.24
This commit is contained in:
@@ -176,7 +176,7 @@ The service name is `kube-dns` for both CoreDNS and kube-dns deployments.
|
||||
|
||||
If you have created the Service or in the case it should be created by default
|
||||
but it does not appear, see
|
||||
[debugging Services](/docs/tasks/debug-application-cluster/debug-service/) for
|
||||
[debugging Services](/docs/tasks/debug/debug-application/debug-service/) for
|
||||
more information.
|
||||
|
||||
### Are DNS endpoints exposed?
|
||||
@@ -193,7 +193,7 @@ kube-dns 10.180.3.17:53,10.180.3.17:53 1h
|
||||
```
|
||||
|
||||
If you do not see the endpoints, see the endpoints section in the
|
||||
[debugging Services](/docs/tasks/debug-application-cluster/debug-service/) documentation.
|
||||
[debugging Services](/docs/tasks/debug/debug-application/debug-service/) documentation.
|
||||
|
||||
For additional Kubernetes DNS examples, see the
|
||||
[cluster-dns examples](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns)
|
||||
|
||||
@@ -11,7 +11,7 @@ weight: 20
|
||||
This page explains how to upgrade a Kubernetes cluster created with kubeadm from version
|
||||
{{< skew currentVersionAddMinor -1 >}}.x to version {{< skew currentVersion >}}.x, and from version
|
||||
{{< skew currentVersion >}}.x to {{< skew currentVersion >}}.y (where `y > x`). Skipping MINOR versions
|
||||
when upgrading is unsupported.
|
||||
when upgrading is unsupported. For more details, please visit [Version Skew Policy](https://kubernetes.io/releases/version-skew-policy/).
|
||||
|
||||
To see information about upgrading clusters created using older versions of kubeadm,
|
||||
please refer to following pages instead:
|
||||
|
||||
+1
-1
@@ -13,7 +13,7 @@ Kubernetes' support for direct integration with Docker Engine is deprecated, and
|
||||
## Telemetry and security agents
|
||||
|
||||
Within a Kubernetes cluster there are a few different ways to run telemetry or security agents.
|
||||
Some agents have a direct dependency on Docker Engine when they as DaemonSets or
|
||||
Some agents have a direct dependency on Docker Engine when they run as DaemonSets or
|
||||
directly on nodes.
|
||||
|
||||
### Why do some telemetry agents communicate with Docker Engine?
|
||||
|
||||
@@ -210,7 +210,7 @@ access to a subset of the keyspace is strongly recommended.
|
||||
|
||||
### Enable audit logging
|
||||
|
||||
The [audit logger](/docs/tasks/debug-application-cluster/audit/) is a beta feature that records actions taken by the
|
||||
The [audit logger](/docs/tasks/debug/debug-cluster/audit/) is a beta feature that records actions taken by the
|
||||
API for later analysis in the event of a compromise. It is recommended to enable audit logging
|
||||
and archive the audit file on a secure server.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user