Merge pull request #39533 from Zhuzhenghao/2-19

[zh] Resync some tiny changes in page under tasks
pull/39549/head
Kubernetes Prow Robot 2023-02-19 03:37:37 -08:00 committed by GitHub
commit 448e1fa0f6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 12 additions and 8 deletions

View File

@ -261,7 +261,7 @@ kubectl get deployment patch-demo --output yaml
The `containers` list that you specified in the patch has only one Container.
The output shows that your list of one Container replaced the existing `containers` list.
```shell
```yaml
spec:
containers:
- image: gcr.io/google-samples/node-hello:1.0

View File

@ -49,7 +49,7 @@ restarts. Here is the configuration file for the Pod:
{{< codenew file="pods/storage/redis.yaml" >}}
<!--
1.Create the Pod:
1. Create the Pod:
-->
1. 创建 Pod:
@ -88,7 +88,7 @@ restarts. Here is the configuration file for the Pod:
```
<!--
1.In your shell, go to `/data/redis`, and then create a file:
1. In your shell, go to `/data/redis`, and then create a file:
-->
4. 在你的 Shell 中,切换到 `/data/redis` 目录下,然后创建一个文件:

View File

@ -356,6 +356,7 @@ For each updated PodSecurityPolicy:
you can compare the pod with the PodTemplate in the controller resource. If any changes are
identified, the original Pod or PodTemplate should be updated with the desired configuration.
The fields to review are:
- `.metadata.annotations['container.apparmor.security.beta.kubernetes.io/*']` (replace * with each container name)
-->
2. 比较运行中的 Pod 与原来的 Pod 规约,确定 PodSecurityPolicy 是否更改过这些 Pod。
对于通过[工作负载资源](/zh-cn/docs/concepts/workloads/controllers/)所创建的 Pod

View File

@ -44,11 +44,11 @@ as an example registry.
<!-- steps -->
<!--
## Log in to Docker
## Log in to Docker Hub
On your laptop, you must authenticate with a registry in order to pull a private image.
-->
## 登录 Docker 镜像仓库 {#log-in-to-docker}
## 登录 Docker 镜像仓库 {#log-in-to-docker-hub}
在个人电脑上,要想拉取私有镜像必须在镜像仓库上进行身份验证。

View File

@ -639,7 +639,7 @@ kubectl patch deployment patch-demo --patch '{"spec": {"template": {"spec": {"co
The flag `--subresource=[subresource-name]` is used with kubectl commands like get, patch,
edit and replace to fetch and update `status` and `scale` subresources of the resources
(applicable for kubectl version v1.24 or more). This flag is used with all the API resources
(built-in and CRs) which has `status` or `scale` subresource. Deployment is one of the
(built-in and CRs) that have `status` or `scale` subresource. Deployment is one of the
examples which supports these subresources.
Here's a manifest for a Deployment that has two replicas:

View File

@ -7,6 +7,8 @@ content_type: task
reviewers:
- lachie83
- khenidak
- bridgetkromhout
min-kubernetes-server-version: v1.23
title: Validate IPv4/IPv6 dual-stack
content_type: task
-->
@ -316,7 +318,7 @@ Events: <none>
<!--
### Create a dual-stack load balanced Service
If the cloud provider supports the provisioning of IPv6 enabled external load balancers, create the following Service with `PreferDualStack` in `.spec.ipFamilyPolicy`. `IPv6` as the first element of the `.spec.ipFamilies` array and the `type` field set to `LoadBalancer`.
If the cloud provider supports the provisioning of IPv6 enabled external load balancers, create the following Service with `PreferDualStack` in `.spec.ipFamilyPolicy`, `IPv6` as the first element of the `.spec.ipFamilies` array and the `type` field set to `LoadBalancer`.
-->
### 创建双协议栈负载均衡服务
@ -336,7 +338,7 @@ kubectl get svc -l app.kubernetes.io/name=MyApp
```
<!--
Validate that the Service receives a `CLUSTER-IP` address from the IPv6 address block along with an `EXTERNAL-IP`. You may then validate access to the service via the IP and port.
Validate that the Service receives a `CLUSTER-IP` address from the IPv6 address block along with an `EXTERNAL-IP`. You may then validate access to the service via the IP and port.
-->
验证服务是否从 IPv6 地址块中接收到 `CLUSTER-IP` 地址以及 `EXTERNAL-IP`
然后,你可以通过 IP 和端口验证对服务的访问。

View File

@ -1,6 +1,7 @@
---
title: 扩缩 StatefulSet
content_type: task
weight: 50
---
<!-- overview -->