Merge pull request #33339 from my-git9/debuglink4
[en] modify link about debug
This commit is contained in:
commit
41dfc83423
|
|
@ -231,7 +231,7 @@ The kubelet reports the resource usage of a Pod as part of the Pod
|
||||||
|
|
||||||
If optional [tools for monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring/)
|
If optional [tools for monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring/)
|
||||||
are available in your cluster, then Pod resource usage can be retrieved either
|
are available in your cluster, then Pod resource usage can be retrieved either
|
||||||
from the [Metrics API](/docs/tasks/debug-application-cluster/resource-metrics-pipeline/#metrics-api)
|
from the [Metrics API](/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/#metrics-api)
|
||||||
directly or from your monitoring tools.
|
directly or from your monitoring tools.
|
||||||
|
|
||||||
## Local ephemeral storage
|
## Local ephemeral storage
|
||||||
|
|
|
||||||
|
|
@ -197,7 +197,7 @@ are some virtualization platforms that can be scripted to spin up new nodes
|
||||||
based on demand.
|
based on demand.
|
||||||
- *Set up node health checks*: For important workloads, you want to make sure
|
- *Set up node health checks*: For important workloads, you want to make sure
|
||||||
that the nodes and pods running on those nodes are healthy. Using the
|
that the nodes and pods running on those nodes are healthy. Using the
|
||||||
[Node Problem Detector](/docs/tasks/debug-application-cluster/monitor-node-health/)
|
[Node Problem Detector](/docs/tasks/debug/debug-cluster/monitor-node-health/)
|
||||||
daemon, you can ensure your nodes are healthy.
|
daemon, you can ensure your nodes are healthy.
|
||||||
|
|
||||||
## Production user management
|
## Production user management
|
||||||
|
|
|
||||||
|
|
@ -163,7 +163,7 @@ services](/docs/concepts/services-networking/service/#type-nodeport) or use `Hos
|
||||||
|
|
||||||
## Pods are not accessible via their Service IP
|
## Pods are not accessible via their Service IP
|
||||||
|
|
||||||
- Many network add-ons do not yet enable [hairpin mode](/docs/tasks/debug-application-cluster/debug-service/#a-pod-fails-to-reach-itself-via-the-service-ip)
|
- Many network add-ons do not yet enable [hairpin mode](/docs/tasks/debug/debug-application/debug-service/#a-pod-fails-to-reach-itself-via-the-service-ip)
|
||||||
which allows pods to access themselves via their Service IP. This is an issue related to
|
which allows pods to access themselves via their Service IP. This is an issue related to
|
||||||
[CNI](https://github.com/containernetworking/cni/issues/476). Please contact the network
|
[CNI](https://github.com/containernetworking/cni/issues/476). Please contact the network
|
||||||
add-on provider to get the latest status of their support for hairpin mode.
|
add-on provider to get the latest status of their support for hairpin mode.
|
||||||
|
|
|
||||||
|
|
@ -609,7 +609,7 @@ None of the Pod [`securityContext`](/docs/reference/kubernetes-api/workload-reso
|
||||||
### Node problem detector
|
### Node problem detector
|
||||||
|
|
||||||
The node problem detector (see
|
The node problem detector (see
|
||||||
[Monitor Node Health](/docs/tasks/debug-application-cluster/monitor-node-health/))
|
[Monitor Node Health](/docs/tasks/debug/debug-cluster/monitor-node-health/))
|
||||||
is not compatible with Windows.
|
is not compatible with Windows.
|
||||||
|
|
||||||
### Pause container
|
### Pause container
|
||||||
|
|
|
||||||
|
|
@ -90,7 +90,7 @@ The common use for HorizontalPodAutoscaler is to configure it to fetch metrics f
|
||||||
(`metrics.k8s.io`, `custom.metrics.k8s.io`, or `external.metrics.k8s.io`). The `metrics.k8s.io` API is
|
(`metrics.k8s.io`, `custom.metrics.k8s.io`, or `external.metrics.k8s.io`). The `metrics.k8s.io` API is
|
||||||
usually provided by an add-on named Metrics Server, which needs to be launched separately.
|
usually provided by an add-on named Metrics Server, which needs to be launched separately.
|
||||||
For more information about resource metrics, see
|
For more information about resource metrics, see
|
||||||
[Metrics Server](/docs/tasks/debug-application-cluster/resource-metrics-pipeline/#metrics-server).
|
[Metrics Server](/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/#metrics-server).
|
||||||
|
|
||||||
[Support for metrics APIs](#support-for-metrics-apis) explains the stability guarantees and support status for these
|
[Support for metrics APIs](#support-for-metrics-apis) explains the stability guarantees and support status for these
|
||||||
different APIs.
|
different APIs.
|
||||||
|
|
|
||||||
|
|
@ -93,7 +93,7 @@ cassandra ClusterIP None <none> 9042/TCP 45s
|
||||||
```
|
```
|
||||||
|
|
||||||
If you don't see a Service named `cassandra`, that means creation failed. Read
|
If you don't see a Service named `cassandra`, that means creation failed. Read
|
||||||
[Debug Services](/docs/tasks/debug-application-cluster/debug-service/)
|
[Debug Services](/docs/tasks/debug/debug-application/debug-service/)
|
||||||
for help troubleshooting common issues.
|
for help troubleshooting common issues.
|
||||||
|
|
||||||
## Using a StatefulSet to create a Cassandra ring
|
## Using a StatefulSet to create a Cassandra ring
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue