Skip to content

Commit a4dd61c

Browse files
hunshcnhunshcn
committed
[zh-cn] fix outdated link/anchor
Signed-off-by: hunshcn <[email protected]>
1 parent 9bf997a commit a4dd61c

File tree

21 files changed

+40
-40
lines changed

21 files changed

+40
-40
lines changed

‎content/zh-cn/blog/_posts/2023-08-24-swap-beta1-graduation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ The available configuration options for `swapBehavior` are:
8686

8787
<!--
8888
- `UnlimitedSwap` (default): Kubernetes workloads can use as much swap memory as they request, up to the system limit.
89-
- `LimitedSwap`: The utilization of swap memory by Kubernetes workloads is subject to limitations. Only Pods of [Burstable](docs/concepts/workloads/pods/pod-qos/#burstable) QoS are permitted to employ swap.
89+
- `LimitedSwap`: The utilization of swap memory by Kubernetes workloads is subject to limitations. Only Pods of [Burstable](/docs/concepts/workloads/pods/pod-qos/#burstable) QoS are permitted to employ swap.
9090
-->
9191
- `UnlimitedSwap`（默认）：Kubernetes 工作负载可以根据请求使用尽可能多的交换内存，最多可达到系统限制。
9292
- `LimitedSwap`：Kubernetes 工作负载对交换内存的使用受到限制。
@@ -261,9 +261,9 @@ Swap configuration on a node is exposed to a cluster admin via the [`memorySwap`
261261
作为集群管理员，你可以通过设置 `memorySwap.swapBehavior` 来指定存在交换内存时节点的行为。
262262

263263
<!--
264-
The kubelet [employs the CRI](https://kubernetes.io/docs/concepts/architecture/cri/) (container runtime interface) API to direct the CRI to configure specific cgroup v2 parameters (such as `memory.swap.max`) in a manner that will enable the desired swap configuration for a container. The CRI is then responsible to write these settings to the container-level cgroup.
264+
The kubelet [employs the CRI](/docs/concepts/architecture/cri/) (container runtime interface) API to direct the CRI to configure specific cgroup v2 parameters (such as `memory.swap.max`) in a manner that will enable the desired swap configuration for a container. The CRI is then responsible to write these settings to the container-level cgroup.
265265
-->
266-
kubelet [使用 CRI](/zh-cn/docs/concepts/architecture/cri)
266+
kubelet [使用 CRI](/zh-cn/docs/concepts/architecture/cri/)
267267
（容器运行时接口）API 来指示 CRI 配置特定的 cgroup v2 参数（例如 `memory.swap.max`），
268268
配置方式要支持容器所期望的交换内存配置。接下来，CRI 负责将这些设置写入容器级的 cgroup。
269269

‎content/zh-cn/blog/_posts/2023-10-05-sig-architecture-conformance-spotlight.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,15 @@ Architecture: Conformance subproject_
2727
In this [SIG
2828
Architecture](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md)
2929
spotlight, we talked with [Riaan
30-
Kleinhans](https://github.com/Riaankl) (ii-Team), Lead for the
30+
Kleinhans](https://github.com/Riaankl) (ii.nz), Lead for the
3131
[Conformance
3232
sub-project](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md#conformance-definition-1).
3333
-->
3434
**这是 SIG Architecture 焦点访谈系列的首次采访，这一系列访谈将涵盖多个子项目。
3535
我们从 SIG Architecture：Conformance 子项目开始。**
3636

3737
在本次 [SIG Architecture](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md)
38-
访谈中，我们与 [Riaan Kleinhans](https://github.com/Riaankl) (ii-Team) 进行了对话，他是
38+
访谈中，我们与 [Riaan Kleinhans](https://github.com/Riaankl) (ii.nz) 进行了对话，他是
3939
[Conformance 子项目](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md#conformance-definition-1)的负责人。
4040

4141
<!--
@@ -45,7 +45,7 @@ sub-project](https://github.com/kubernetes/community/blob/master/sig-architectur
4545
bit about yourself, your role and how you got involved in Kubernetes.
4646
4747
**Riaan Kleinhans (RK)**: Hi! My name is Riaan Kleinhans and I live in
48-
South Africa. I am the Project manager for the [ii-Team](ii.nz) in New
48+
South Africa. I am the Project manager for the [ii.nz](https://ii.nz) in New
4949
Zealand. When I joined ii the plan was to move to New Zealand in April
5050
2020 and then Covid happened. Fortunately, being a flexible and
5151
dynamic team we were able to make it work remotely and in very
@@ -56,7 +56,7 @@ different time zones.
5656
**Frederico (FSM)**：你好 Riaan，欢迎！首先，请介绍一下你自己，你的角色以及你是如何参与 Kubernetes 的。
5757

5858
**Riaan Kleinhans (RK)**：嗨！我叫 Riaan Kleinhans，我住在南非。
59-
我是新西兰 [ii-Team](ii.nz) 的项目经理。在我加入 ii 时，本来计划在 2020 年 4 月搬到新西兰，
59+
我是新西兰 [ii.nz](https://ii.nz) 的项目经理。在我加入 ii 时，本来计划在 2020 年 4 月搬到新西兰，
6060
然后新冠疫情爆发了。幸运的是，作为一个灵活和富有活力的团队，我们能够在各个不同的时区以远程方式协作。
6161

6262
<!--

‎content/zh-cn/docs/concepts/cluster-administration/flow-control.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ APF 适用于 **watch** 请求。当 APF 被禁用时，**watch** 请求不受 `
8282
<!--
8383
The API Priority and Fairness feature is controlled by a command-line flag
8484
and is enabled by default. See
85-
[Options](/docs/reference/command-line-tools-reference/kube-apiserver/options/)
85+
[Options](/docs/reference/command-line-tools-reference/kube-apiserver/#options)
8686
for a general explanation of the available kube-apiserver command-line
8787
options and how to enable and disable them. The name of the
8888
command-line option for APF is "--enable-priority-and-fairness". This feature
@@ -94,7 +94,7 @@ disable the API group beta version `v1beta3` by adding the
9494
-->
9595
API 优先级与公平性（APF）特性由命令行标志控制，默认情况下启用。
9696
有关可用 kube-apiserver 命令行参数以及如何启用和禁用的说明，
97-
请参见[参数](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/options/)。
97+
请参见[参数](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/#options)。
9898
APF 的命令行参数是 "--enable-priority-and-fairness"。
9999
此特性也与某个 {{< glossary_tooltip term_id="api-group" text="API 组" >}}相关：
100100
(a) 稳定的 `v1` 版本，在 1.29 中引入，默认启用；

‎content/zh-cn/docs/concepts/configuration/secret.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -398,12 +398,12 @@ You should only create a ServiceAccount token Secret
398398
if you can't use the `TokenRequest` API to obtain a token,
399399
and the security exposure of persisting a non-expiring token credential
400400
in a readable API object is acceptable to you. For instructions, see
401-
[Manually create a long-lived API token for a ServiceAccount](/docs/tasks/configure-pod-container/configure-service-account/#manually-create-a-service-account-api-token).
401+
[Manually create a long-lived API token for a ServiceAccount](/docs/tasks/configure-pod-container/configure-service-account/#manually-create-an-api-token-for-a-serviceaccount).
402402
-->
403403
只有在你无法使用 `TokenRequest` API 来获取令牌，
404404
并且你能够接受因为将永不过期的令牌凭据写入到可读取的 API 对象而带来的安全风险时，
405405
才应该创建 ServiceAccount 令牌 Secret。
406-
更多细节参阅[为 ServiceAccount 手动创建长期有效的 API 令牌](/zh-cn/docs/tasks/configure-pod-container/configure-service-account/#manually-create-a-service-account-api-token)。
406+
更多细节参阅[为 ServiceAccount 手动创建长期有效的 API 令牌](/zh-cn/docs/tasks/configure-pod-container/configure-service-account/#manually-create-an-api-token-for-a-serviceaccount)。
407407
{{< /note >}}
408408

409409
<!--

‎content/zh-cn/docs/concepts/extend-kubernetes/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -500,7 +500,7 @@ a way to extend Kubernetes with supports for new kinds of volumes. The volumes c
500500
durable external storage, or provide ephemeral storage, or they might offer a read-only interface
501501
to information using a filesystem paradigm.
502502
503-
Kubernetes also includes support for [FlexVolume](/docs/concepts/storage/volumes/#flexvolume-deprecated) plugins,
503+
Kubernetes also includes support for [FlexVolume](/docs/concepts/storage/volumes/#flexvolume) plugins,
504504
which are deprecated since Kubernetes v1.23 (in favour of CSI).
505505
-->
506506
### 存储插件 {#storage-plugins}
@@ -509,7 +509,7 @@ which are deprecated since Kubernetes v1.23 (in favour of CSI).
509509
Kubernetes 的方式使其支持新类别的卷。
510510
这些卷可以由持久的外部存储提供支持，可以提供临时存储，还可以使用文件系统范型为信息提供只读接口。
511511

512-
Kubernetes 还包括对 [FlexVolume](/zh-cn/docs/concepts/storage/volumes/#flexvolume-deprecated)
512+
Kubernetes 还包括对 [FlexVolume](/zh-cn/docs/concepts/storage/volumes/#flexvolume)
513513
插件的支持，该插件自 Kubernetes v1.23 起被弃用（被 CSI 替代）。
514514

515515
<!--

‎content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,10 +88,10 @@ documentation for that Container Runtime, for example:
8888

8989
<!--
9090
For specific information about how to install and manage a CNI plugin, see the documentation for
91-
that plugin or [networking provider](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model).
91+
that plugin or [networking provider](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-network-model).
9292
-->
9393
要了解如何安装和管理 CNI 插件的具体信息，可参阅对应的插件或
94-
[网络驱动（Networking Provider）](/zh-cn/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model)
94+
[网络驱动（Networking Provider）](/zh-cn/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-network-model)
9595
的文档。
9696

9797
<!--

‎content/zh-cn/docs/contribute/new-content/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ Scenario | Branch
146146
:---------|:------------
147147
Existing or new English language content for the current release | `main`
148148
Content for a feature change release | The branch which corresponds to the major and minor version the feature change is in, using the pattern `dev-<version>`. For example, if a feature changes in the `v{{< skew nextMinorVersion >}}` release, then add documentation changes to the ``dev-{{< skew nextMinorVersion >}}`` branch.
149-
Content in other languages (localizations) | Use the localization's convention. See the [Localization branching strategy](/docs/contribute/localization/#branching-strategy) for more information.
149+
Content in other languages (localizations) | Use the localization's convention. See the [Localization branching strategy](/docs/contribute/localization/#branch-strategy) for more information.
150150
151151
If you're still not sure which branch to choose, ask in `#sig-docs` on Slack.
152152
-->
@@ -159,7 +159,7 @@ If you're still not sure which branch to choose, ask in `#sig-docs` on Slack.
159159
:---------|:------------
160160
针对当前发行版本的，对现有英文内容的修改或新的英文内容 | `main`
161161
针对功能特性变更的内容 | 分支对应于功能特性变更的主要和次要版本，分支名称采用 `dev-<version>` 的模式。例如，如果某功能特性在 `v{{< skew nextMinorVersion >}}` 版本发生变化，则对应的文档变化要添加到 `dev-{{< skew nextMinorVersion >}}` 分支。
162-
其他语言的内容（本地化） | 基于本地化团队的约定。参见[本地化分支策略](/zh-cn/docs/contribute/localization/#branching-strategy)了解更多信息。
162+
其他语言的内容（本地化） | 基于本地化团队的约定。参见[本地化分支策略](/zh-cn/docs/contribute/localization/#branch-strategy)了解更多信息。
163163

164164
如果你仍不能确定要选择哪个分支，请在 Slack 的 `#sig-docs` 频道上提出问题。
165165

‎content/zh-cn/docs/reference/command-line-tools-reference/feature-gates/custom-pod-dns.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ removed: true
2525
---
2626
<!--
2727
Enable customizing the DNS settings for a Pod using its `dnsConfig` property.
28-
Check [Pod's DNS Config](/docs/concepts/services-networking/dns-pod-service/#pods-dns-config)
28+
Check [Pod's DNS Config](/docs/concepts/services-networking/dns-pod-service/#pod-dns-config)
2929
for more details.
3030
-->
3131
允许使用 Pod 的 `dnsConfig` 属性自定义其 DNS 设置。
3232
更多详细信息，请参见
33-
[Pod 的 DNS 配置](/zh-cn/docs/concepts/services-networking/dns-pod-service/#pods-dns-config)。
33+
[Pod 的 DNS 配置](/zh-cn/docs/concepts/services-networking/dns-pod-service/#pod-dns-config)。

‎content/zh-cn/docs/reference/command-line-tools-reference/feature-gates/network-policy-end-port.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ removed: true
2424

2525
<!--
2626
Allows you to define ports in a
27-
[NetworkPolicy](docs/concepts/services-networking/network-policies/)
27+
[NetworkPolicy](/docs/concepts/services-networking/network-policies/)
2828
rule as a range of port numbers.
2929
-->
3030
允许你在 [NetworkPolicy](/zh-cn/docs/concepts/services-networking/network-policies/)

‎content/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ API 服务器为 REST 操作提供服务，并为集群的共享状态提供前
2121
kube-apiserver [flags]
2222
```
2323

24-
## {{% heading "options" %}}
24+
## {{% heading "options" %}} {#options}
2525

2626
<table style="width: 100%; table-layout: fixed;">
2727
<colgroup>

‎content/zh-cn/docs/reference/using-api/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Kubernetes API 服务器进行身份认证以及他们的请求如何被鉴权
6464
<!--
6565
## API versioning
6666
-->
67-
## API 版本控制 {#api-reference}
67+
## API 版本控制 {#api-versioning}
6868

6969
<!--
7070
The JSON and Protobuf serialization schemas follow the same guidelines for

‎content/zh-cn/docs/setup/production-environment/container-runtimes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -640,6 +640,6 @@ The command line argument to use is `--pod-infra-container-image`.
640640

641641
<!--
642642
As well as a container runtime, your cluster will need a working
643-
[network plugin](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model).
643+
[network plugin](/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-network-model).
644644
-->
645-
除了容器运行时，你的集群还需要有效的[网络插件](/zh-cn/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-networking-model)。
645+
除了容器运行时，你的集群还需要有效的[网络插件](/zh-cn/docs/concepts/cluster-administration/networking/#how-to-implement-the-kubernetes-network-model)。

‎content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -538,12 +538,12 @@ systemctl enable --now kubelet
538538
<!--
539539
The Flatcar Container Linux distribution mounts the `/usr` directory as a read-only filesystem.
540540
Before bootstrapping your cluster, you need to take additional steps to configure a writable directory.
541-
See the [Kubeadm Troubleshooting guide](/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#usr-mounted-read-only/)
541+
See the [Kubeadm Troubleshooting guide](/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#usr-mounted-read-only)
542542
to learn how to set up a writable directory.
543543
-->
544544
Flatcar Container Linux 发行版会将 `/usr/` 目录挂载为一个只读文件系统。
545545
在启动引导你的集群之前，你需要执行一些额外的操作来配置一个可写入的目录。
546-
参见 [kubeadm 故障排查指南](/zh-cn/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#usr-mounted-read-only/)
546+
参见 [kubeadm 故障排查指南](/zh-cn/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/#usr-mounted-read-only)
547547
以了解如何配置一个可写入的目录。
548548
{{< /note >}}
549549

‎content/zh-cn/docs/tasks/access-application-cluster/access-cluster-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -146,11 +146,11 @@ if suitable credentials are passed, or through a kubectl proxy at, for example:
146146
`http://localhost:8080/api/v1/namespaces/kube-system/services/elasticsearch-logging/proxy/`。
147147

148148
<!--
149-
See [Access Clusters Using the Kubernetes API](/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-cluster-api)
149+
See [Access Clusters Using the Kubernetes API](/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-kubernetes-api)
150150
for how to pass credentials or use kubectl proxy.
151151
-->
152152
{{< note >}}
153-
请参阅[使用 Kubernetes API 访问集群](/zh-cn/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-cluster-api)
153+
请参阅[使用 Kubernetes API 访问集群](/zh-cn/docs/tasks/administer-cluster/access-cluster-api/#accessing-the-kubernetes-api)
154154
了解如何传递凭据或如何使用 `kubectl proxy`。
155155
{{< /note >}}
156156

‎content/zh-cn/docs/tasks/administer-cluster/access-cluster-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This page shows how to access clusters using the Kubernetes API.
2727
2828
### Accessing for the first time with kubectl
2929
-->
30-
## 访问 Kubernetes API
30+
## 访问 Kubernetes API {#accessing-the-kubernetes-api}
3131

3232
### 使用 kubectl 进行首次访问
3333

‎content/zh-cn/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The page also provides details on how to set up a number of different container
5454
<!--
5555
## Configuring the kubelet cgroup driver
5656
-->
57-
## 配置 kubelet 的 cgroup 驱动
57+
## 配置 kubelet 的 cgroup 驱动 {#configuring-the-kubelet-cgroup-driver}
5858

5959
<!--
6060
kubeadm allows you to pass a `KubeletConfiguration` structure during `kubeadm init`.

‎content/zh-cn/docs/tasks/configure-pod-container/configure-pod-initialization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ container starts.
3232
3333
Here is the configuration file for the Pod:
3434
-->
35-
## 创建一个包含 Init 容器的 Pod {#creating-a-pod-that-has-an-init-container}
35+
## 创建一个包含 Init 容器的 Pod {#create-a-pod-that-has-an-init-container}
3636

3737
本例中你将创建一个包含一个应用容器和一个 Init 容器的 Pod。Init 容器在应用容器启动前运行完成。
3838

‎content/zh-cn/docs/tasks/debug/debug-application/debug-init-containers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,11 +37,11 @@ Init Containers. The example command lines below refer to the Pod as
3737
<!--
3838
* You should be familiar with the basics of
3939
[Init Containers](/docs/concepts/workloads/pods/init-containers/).
40-
* You should have [Configured an Init Container](/docs/tasks/configure-pod-container/configure-pod-initialization/#creating-a-pod-that-has-an-init-container/).
40+
* You should have [Configured an Init Container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container).
4141
-->
4242

4343
* 你应该熟悉 [Init 容器](/zh-cn/docs/concepts/workloads/pods/init-containers/)的基础知识。
44-
* 你应该已经[配置好一个 Init 容器](/zh-cn/docs/tasks/configure-pod-container/configure-pod-initialization/#creating-a-pod-that-has-an-init-container/)。
44+
* 你应该已经[配置好一个 Init 容器](/zh-cn/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container)。
4545

4646
<!-- steps -->
4747

‎content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -636,14 +636,14 @@ which caused the conversion. All other changes are ignored.
636636
### Deploy the conversion webhook service
637637

638638
Documentation for deploying the conversion webhook is the same as for the
639-
[admission webhook example service](/docs/reference/access-authn-authz/extensible-admission-controllers/#deploy_the_admission_webhook_service).
639+
[admission webhook example service](/docs/reference/access-authn-authz/extensible-admission-controllers/#deploy-the-admission-webhook-service).
640640
The assumption for next sections is that the conversion webhook server is deployed to a service
641641
named `example-conversion-webhook-server` in `default` namespace and serving traffic on path `/crdconvert`.
642642
-->
643643
### 部署转换 Webhook 服务 {#deploy-the-conversion-webhook-service}
644644

645645
用于部署转换 Webhook
646-
的文档与[准入 Webhook 服务示例](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/#deploy_the_admission_webhook_service)相同。
646+
的文档与[准入 Webhook 服务示例](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/#deploy-the-admission-webhook-service)相同。
647647
这里的假设是转换 Webhook 服务器被部署为 `default` 名字空间中名为
648648
`example-conversion-webhook-server` 的服务，并在路径 `/crdconvert`
649649
上处理请求。

‎content/zh-cn/docs/tasks/inject-data-application/distribute-credentials-secure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -362,7 +362,7 @@ in octal.
362362
<!--
363363
## Define container environment variables using Secret data
364364
-->
365-
## 使用 Secret 数据定义容器变量 {#define-container-env-var-using-secret-data}
365+
## 使用 Secret 数据定义容器变量 {#define-container-environment-variables-using-secret-data}
366366

367367
<!--
368368
You can consume the data in Secrets as environment variables in your

0 commit comments

Comments
 (0)