kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

sync node-shutdown images crictl

This commit is contained in:
xin gu 2025-03-11 13:57:46 +08:00
parent 72dbe9ccb5
commit 51b2b3ddca
3 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/zh-cn/docs/concepts/cluster-administration/node-shutdown.md
View File

@ -196,7 +196,7 @@ Message: Pod was terminated in response to imminent node shutdown.
To provide more flexibility during graceful node shutdown around the ordering To provide more flexibility during graceful node shutdown around the ordering
of pods during shutdown, graceful node shutdown honors the PriorityClass for of pods during shutdown, graceful node shutdown honors the PriorityClass for
Pods, provided that you enabled this feature in your cluster. The feature Pods, provided that you enabled this feature in your cluster. The feature
allows cluster administers to explicitly define the ordering of pods allows cluster administrators to explicitly define the ordering of pods
during graceful node shutdown based on during graceful node shutdown based on
[priority classes](/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass). [priority classes](/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass).
--> -->

4
content/zh-cn/docs/concepts/containers/images.md
View File

@ -868,7 +868,7 @@ common use cases and suggested solutions.
- Or, run an internal private registry behind your firewall with open read access. - Or, run an internal private registry behind your firewall with open read access.
- No Kubernetes configuration is required. - No Kubernetes configuration is required.
- Use a hosted container image registry service that controls image access - Use a hosted container image registry service that controls image access
- It will work better with cluster autoscaling than manual node configuration. - It will work better with Node autoscaling than manual node configuration.
- Or, on a cluster where changing the node configuration is inconvenient, use `imagePullSecrets`. - Or, on a cluster where changing the node configuration is inconvenient, use `imagePullSecrets`.
--> -->
2. 集群运行一些专有镜像，这些镜像需要对公司外部隐藏，对所有集群用户可见 2. 集群运行一些专有镜像，这些镜像需要对公司外部隐藏，对所有集群用户可见
@ -877,7 +877,7 @@ common use cases and suggested solutions.
- 或者，在防火墙内运行一个组织内部的私有仓库，并开放读取权限 - 或者，在防火墙内运行一个组织内部的私有仓库，并开放读取权限
- 不需要配置 Kubernetes - 不需要配置 Kubernetes
- 使用控制镜像访问的托管容器镜像仓库服务 - 使用控制镜像访问的托管容器镜像仓库服务
- 与手动配置节点相比，这种方案能更好地处理集群自动扩缩容 - 与手动配置节点相比，这种方案能更好地处理节点自动扩缩容
- 或者，在不方便更改节点配置的集群中，使用 `imagePullSecrets` - 或者，在不方便更改节点配置的集群中，使用 `imagePullSecrets`
<!-- <!--

2
content/zh-cn/docs/tasks/debug/debug-cluster/crictl.md
View File

@ -370,7 +370,5 @@ The output is similar to this:
<!-- <!--
* [Learn more about `crictl`](https://github.com/kubernetes-sigs/cri-tools). * [Learn more about `crictl`](https://github.com/kubernetes-sigs/cri-tools).
* [Map `docker` CLI commands to `crictl`](/docs/reference/tools/map-crictl-dockercli/).
--> -->
* [进一步了解 `crictl`](https://github.com/kubernetes-sigs/cri-tools) * [进一步了解 `crictl`](https://github.com/kubernetes-sigs/cri-tools)
* [将 `docker` CLI 命令映射到 `crictl`](/zh-cn/docs/reference/tools/map-crictl-dockercli/)