From 82c2343e7b18559cce7dc49e7cfdccbe0042236d Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Sun, 19 Mar 2023 22:45:34 +0900 Subject: [PATCH 01/12] copy tutorials/services/pods-and-endpoint-termination-flow --- .../pods-and-endpoint-termination-flow.md | 221 ++++++++++++++++++ .../pod-with-graceful-termination.yaml | 32 +++ 2 files changed, 253 insertions(+) create mode 100644 content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md create mode 100644 content/ja/examples/service/pod-with-graceful-termination.yaml diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md new file mode 100644 index 0000000000..3ff7e2d987 --- /dev/null +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -0,0 +1,221 @@ +--- +title: Explore Termination Behavior for Pods And Their Endpoints +content_type: tutorial +weight: 60 +--- + + + + +Once you connected your Application with Service following steps +like those outlined in [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/), +you have a continuously running, replicated application, that is exposed on a network. +This tutorial helps you look at the termination flow for Pods and to explore ways to implement +graceful connection draining. + + + +## Termination process for Pods and their endpoints + +There are often cases when you need to terminate a Pod - be it for upgrade or scale down. +In order to improve application availability, it may be important to implement +a proper active connections draining. This tutorial explains the flow of +Pod termination in connection with the corresponding endpoint state and removal. + +This tutorial explains the flow of Pod termination in connection with the +corresponding endpoint state and removal by using +a simple nginx web server to demonstrate the concept. + + + +## Example flow with endpoint termination + +The following is the example of the flow described in the +[Termination of Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination) +document. + +Let's say you have a Deployment containing of a single `nginx` replica +(just for demonstration purposes) and a Service: + +{{< codenew file="service/pod-with-graceful-termination.yaml" >}} + +```yaml +apiVersion: apps/v1 +kind: Deployment +metadata: + name: nginx-deployment + labels: + app: nginx +spec: + replicas: 1 + selector: + matchLabels: + app: nginx + template: + metadata: + labels: + app: nginx + spec: + terminationGracePeriodSeconds: 120 # extra long grace period + containers: + - name: nginx + image: nginx:latest + ports: + - containerPort: 80 + lifecycle: + preStop: + exec: + # Real life termination may take any time up to terminationGracePeriodSeconds. + # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, + # at 120 seconds container will be forcibly terminated. + # Note, all this time nginx will keep processing requests. + command: [ + "/bin/sh", "-c", "sleep 180" + ] + +--- + +apiVersion: v1 +kind: Service +metadata: + name: nginx-service +spec: + selector: + app: nginx + ports: + - protocol: TCP + port: 80 + targetPort: 80 +``` + +Once the Pod and Service are running, you can get the name of any associated EndpointSlices: + +```shell +kubectl get endpointslice +``` + +The output is similar to this: + +```none +NAME ADDRESSTYPE PORTS ENDPOINTS AGE +nginx-service-6tjbr IPv4 80 10.12.1.199,10.12.1.201 22m +``` + +You can see its status, and validate that there is one endpoint registered: + +```shell +kubectl get endpointslices -o json -l kubernetes.io/service-name=nginx-service +``` + +The output is similar to this: + +```none +{ + "addressType": "IPv4", + "apiVersion": "discovery.k8s.io/v1", + "endpoints": [ + { + "addresses": [ + "10.12.1.201" + ], + "conditions": { + "ready": true, + "serving": true, + "terminating": false +``` + +Now let's terminate the Pod and validate that the Pod is being terminated +respecting the graceful termination period configuration: + +```shell +kubectl delete pod nginx-deployment-7768647bf9-b4b9s +``` + +All pods: + +```shell +kubectl get pods +``` + +The output is similar to this: + +```none +NAME READY STATUS RESTARTS AGE +nginx-deployment-7768647bf9-b4b9s 1/1 Terminating 0 4m1s +nginx-deployment-7768647bf9-rkxlw 1/1 Running 0 8s +``` + +You can see that the new pod got scheduled. + +While the new endpoint is being created for the new Pod, the old endpoint is +still around in the terminating state: + +```shell +kubectl get endpointslice -o json nginx-service-6tjbr +``` + +The output is similar to this: + +```none +{ + "addressType": "IPv4", + "apiVersion": "discovery.k8s.io/v1", + "endpoints": [ + { + "addresses": [ + "10.12.1.201" + ], + "conditions": { + "ready": false, + "serving": true, + "terminating": true + }, + "nodeName": "gke-main-default-pool-dca1511c-d17b", + "targetRef": { + "kind": "Pod", + "name": "nginx-deployment-7768647bf9-b4b9s", + "namespace": "default", + "uid": "66fa831c-7eb2-407f-bd2c-f96dfe841478" + }, + "zone": "us-central1-c" + }, + { + "addresses": [ + "10.12.1.202" + ], + "conditions": { + "ready": true, + "serving": true, + "terminating": false + }, + "nodeName": "gke-main-default-pool-dca1511c-d17b", + "targetRef": { + "kind": "Pod", + "name": "nginx-deployment-7768647bf9-rkxlw", + "namespace": "default", + "uid": "722b1cbe-dcd7-4ed4-8928-4a4d0e2bbe35" + }, + "zone": "us-central1-c" +``` + +This allows applications to communicate their state during termination +and clients (such as load balancers) to implement a connections draining functionality. +These clients may detect terminating endpoints and implement a special logic for them. + +In Kubernetes, endpoints that are terminating always have their `ready` status set as as `false`. +This needs to happen for backward +compatibility, so existing load balancers will not use it for regular traffic. +If traffic draining on terminating pod is needed, the actual readiness can be +checked as a condition `serving`. + +When Pod is deleted, the old endpoint will also be deleted. + + +## {{% heading "whatsnext" %}} + + +* Learn how to [Connect Applications with Services](/docs/tutorials/services/connect-applications-service/) +* Learn more about [Using a Service to Access an Application in a Cluster](/docs/tasks/access-application-cluster/service-access-application-cluster/) +* Learn more about [Connecting a Front End to a Back End Using a Service](/docs/tasks/access-application-cluster/connecting-frontend-backend/) +* Learn more about [Creating an External Load Balancer](/docs/tasks/access-application-cluster/create-external-load-balancer/) + diff --git a/content/ja/examples/service/pod-with-graceful-termination.yaml b/content/ja/examples/service/pod-with-graceful-termination.yaml new file mode 100644 index 0000000000..4a39d2d368 --- /dev/null +++ b/content/ja/examples/service/pod-with-graceful-termination.yaml @@ -0,0 +1,32 @@ +apiVersion: apps/v1 +kind: Deployment +metadata: + name: nginx-deployment + labels: + app: nginx +spec: + replicas: 1 + selector: + matchLabels: + app: nginx + template: + metadata: + labels: + app: nginx + spec: + terminationGracePeriodSeconds: 120 # extra long grace period + containers: + - name: nginx + image: nginx:latest + ports: + - containerPort: 80 + lifecycle: + preStop: + exec: + # Real life termination may take any time up to terminationGracePeriodSeconds. + # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, + # at 120 seconds container will be forcibly terminated. + # Note, all this time nginx will keep processing requests. + command: [ + "/bin/sh", "-c", "sleep 180" + ] From 5fe6eddbe7e66bca52beafd94eb2d5dbb66aa6f8 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Sun, 19 Mar 2023 22:50:16 +0900 Subject: [PATCH 02/12] translate tutorials/services/pods-and-endpoint-termination-flow --- .../pods-and-endpoint-termination-flow.md | 86 ++++++++----------- .../pod-with-graceful-termination.yaml | 10 +-- 2 files changed, 40 insertions(+), 56 deletions(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index 3ff7e2d987..eb931ede72 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -1,5 +1,5 @@ --- -title: Explore Termination Behavior for Pods And Their Endpoints +title: Podとそのエンドポイントの終了動作を探る content_type: tutorial weight: 60 --- @@ -7,35 +7,25 @@ weight: 60 -Once you connected your Application with Service following steps -like those outlined in [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/), -you have a continuously running, replicated application, that is exposed on a network. -This tutorial helps you look at the termination flow for Pods and to explore ways to implement -graceful connection draining. +[アプリケーションをサービスに接続する](/docs/tutorials/services/connect-applications-service/)で概略を示したステップに従ってアプリケーションをServiceに接続すると、ネットワーク上で公開され、継続的に実行されて、複製されたアプリケーションが得られます。 +このチュートリアルでは、Podを終了する流れを見て、graceful(上品)な接続ドレインを実装する手法を模索するための手助けをします。 -## Termination process for Pods and their endpoints +## Podの終了手続きとそのエンドポイント -There are often cases when you need to terminate a Pod - be it for upgrade or scale down. -In order to improve application availability, it may be important to implement -a proper active connections draining. This tutorial explains the flow of -Pod termination in connection with the corresponding endpoint state and removal. +アップグレードやスケールダウンのために、Podを終了しなければならない場面はままあります。 +アプリケーションの可用性を高めるために、適切なアクティブ接続ドレインを実装することは重要でしょう。 -This tutorial explains the flow of Pod termination in connection with the -corresponding endpoint state and removal by using -a simple nginx web server to demonstrate the concept. +このチュートリアルでは概念のデモンストレーションのために、シンプルなnginx Webサーバーを例として、関連付けられたエンドポイントステートに接続するPodの終了および削除の流れを説明します。 -## Example flow with endpoint termination +## エンドポイント終了の流れの例 -The following is the example of the flow described in the -[Termination of Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination) -document. +以下は、[Podの終了](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)ドキュメントに記載されている流れの例です。 -Let's say you have a Deployment containing of a single `nginx` replica -(just for demonstration purposes) and a Service: +1つの`nginx`レプリカを含むDeployment(純粋にデモンストレーション目的です)とServiceがあるとします: {{< codenew file="service/pod-with-graceful-termination.yaml" >}} @@ -56,7 +46,7 @@ spec: labels: app: nginx spec: - terminationGracePeriodSeconds: 120 # extra long grace period + terminationGracePeriodSeconds: 120 # 追加の長いgraceful期間 containers: - name: nginx image: nginx:latest @@ -65,10 +55,10 @@ spec: lifecycle: preStop: exec: - # Real life termination may take any time up to terminationGracePeriodSeconds. - # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, - # at 120 seconds container will be forcibly terminated. - # Note, all this time nginx will keep processing requests. + # 実際の活動終了はterminationGracePeriodSecondsまでかかる可能性がある。 + # この例においては、少なくともterminationGracePeriodSecondsの間は待機し、 + # 120秒経過すると、コンテナは強制終了される。 + # この間ずっとnginxはリクエストを処理し続けていることに注意。 command: [ "/bin/sh", "-c", "sleep 180" ] @@ -88,26 +78,26 @@ spec: targetPort: 80 ``` -Once the Pod and Service are running, you can get the name of any associated EndpointSlices: +PodとServiceが実行中になったら、関連付けられたEndpointSlicesの名前を得られます: ```shell kubectl get endpointslice ``` -The output is similar to this: +この出力は以下のようなものになります: ```none NAME ADDRESSTYPE PORTS ENDPOINTS AGE nginx-service-6tjbr IPv4 80 10.12.1.199,10.12.1.201 22m ``` -You can see its status, and validate that there is one endpoint registered: +状態からわかるように、1つのエンドポイントが登録されていることが確認できます: ```shell kubectl get endpointslices -o json -l kubernetes.io/service-name=nginx-service ``` -The output is similar to this: +この出力は以下のようなものになります: ```none { @@ -124,20 +114,19 @@ The output is similar to this: "terminating": false ``` -Now let's terminate the Pod and validate that the Pod is being terminated -respecting the graceful termination period configuration: +では、Podを終了し、そのPodがgracefulな終了期間設定を守って終了されていることを確認してみましょう: ```shell kubectl delete pod nginx-deployment-7768647bf9-b4b9s ``` -All pods: +全Podについて調べます: ```shell kubectl get pods ``` -The output is similar to this: +この出力は以下のようなものになります: ```none NAME READY STATUS RESTARTS AGE @@ -145,16 +134,15 @@ nginx-deployment-7768647bf9-b4b9s 1/1 Terminating 0 4m1s nginx-deployment-7768647bf9-rkxlw 1/1 Running 0 8s ``` -You can see that the new pod got scheduled. +新しいPodがスケジュールされたことを見てとれます。 -While the new endpoint is being created for the new Pod, the old endpoint is -still around in the terminating state: +新しいPodのために新しいエンドポイントが作成される間、古いエンドポイントは終了中の状態のまま残っています: ```shell kubectl get endpointslice -o json nginx-service-6tjbr ``` -The output is similar to this: +この出力は以下のようなものになります: ```none { @@ -198,24 +186,20 @@ The output is similar to this: "zone": "us-central1-c" ``` -This allows applications to communicate their state during termination -and clients (such as load balancers) to implement a connections draining functionality. -These clients may detect terminating endpoints and implement a special logic for them. -In Kubernetes, endpoints that are terminating always have their `ready` status set as as `false`. -This needs to happen for backward -compatibility, so existing load balancers will not use it for regular traffic. -If traffic draining on terminating pod is needed, the actual readiness can be -checked as a condition `serving`. +これを使うと、終了中のアプリケーションがその状態について、接続ドレイン機能の実装目的でクライアント(ロードバランサーなど)と通信する、ということが可能です。 +これらのクライアントではエンドポイントの終了を検出し、そのための特別なロジックを実装できます。 -When Pod is deleted, the old endpoint will also be deleted. +Kubernetesでは、終了中のエンドポイントの`ready`状態は全て`false`にセットされます。 +これは後方互換性のために必要な措置で、既存のロードバランサーは通常のトラフィックにはそれを使用しません。 +Podの終了時にトラフィックのドレインが必要な場合、実際に準備できているかは`serving`状態として調べられます。 +Podが削除される時には、古いエンドポイントも削除されます。 ## {{% heading "whatsnext" %}} -* Learn how to [Connect Applications with Services](/docs/tutorials/services/connect-applications-service/) -* Learn more about [Using a Service to Access an Application in a Cluster](/docs/tasks/access-application-cluster/service-access-application-cluster/) -* Learn more about [Connecting a Front End to a Back End Using a Service](/docs/tasks/access-application-cluster/connecting-frontend-backend/) -* Learn more about [Creating an External Load Balancer](/docs/tasks/access-application-cluster/create-external-load-balancer/) - +* [アプリケーションをサービスに接続する](/docs/tutorials/services/connect-applications-service/)方法を学びます。 +* [Serviceを利用したクラスター内のアプリケーションへのアクセス](/docs/tasks/access-application-cluster/service-access-application-cluster/)を学びます。 +* [Serviceを使用してフロントエンドをバックエンドに接続する](/docs/tasks/access-application-cluster/connecting-frontend-backend/)を学びます。 +* [外部ロードバランサーの作成](/docs/tasks/access-application-cluster/create-external-load-balancer/)を学びます。 diff --git a/content/ja/examples/service/pod-with-graceful-termination.yaml b/content/ja/examples/service/pod-with-graceful-termination.yaml index 4a39d2d368..395a53f5bd 100644 --- a/content/ja/examples/service/pod-with-graceful-termination.yaml +++ b/content/ja/examples/service/pod-with-graceful-termination.yaml @@ -14,7 +14,7 @@ spec: labels: app: nginx spec: - terminationGracePeriodSeconds: 120 # extra long grace period + terminationGracePeriodSeconds: 120 # 追加の長いgraceful期間 containers: - name: nginx image: nginx:latest @@ -23,10 +23,10 @@ spec: lifecycle: preStop: exec: - # Real life termination may take any time up to terminationGracePeriodSeconds. - # In this example - just hang around for at least the duration of terminationGracePeriodSeconds, - # at 120 seconds container will be forcibly terminated. - # Note, all this time nginx will keep processing requests. + # 実際の活動終了はterminationGracePeriodSecondsまでかかる可能性がある。 + # この例においては、少なくともterminationGracePeriodSecondsの間は待機し、 + # 120秒経過すると、コンテナは強制的に終了される。 + # この間ずっとnginxはリクエストを処理し続けていることに注意。 command: [ "/bin/sh", "-c", "sleep 180" ] From fb653ae35ebc6131be81514f6a4a7ca4aa9a8684 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Wed, 22 Mar 2023 19:50:39 +0900 Subject: [PATCH 03/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: nasa9084 --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index eb931ede72..245386301f 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -7,7 +7,7 @@ weight: 60 -[アプリケーションをサービスに接続する](/docs/tutorials/services/connect-applications-service/)で概略を示したステップに従ってアプリケーションをServiceに接続すると、ネットワーク上で公開され、継続的に実行されて、複製されたアプリケーションが得られます。 +[アプリケーションをServiceに接続する](/docs/tutorials/services/connect-applications-service/)で概略を示したステップに従ってアプリケーションをServiceに接続すると、ネットワーク上で公開され、継続的に実行されて、複製されたアプリケーションが得られます。 このチュートリアルでは、Podを終了する流れを見て、graceful(上品)な接続ドレインを実装する手法を模索するための手助けをします。 From f2c20f5f6645fd339d649e5663f103410db0c949 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Wed, 22 Mar 2023 19:51:21 +0900 Subject: [PATCH 04/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: nasa9084 --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index 245386301f..9facb8d43b 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -23,7 +23,7 @@ weight: 60 ## エンドポイント終了の流れの例 -以下は、[Podの終了](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)ドキュメントに記載されている流れの例です。 +以下は、[Podの終了](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)ドキュメントに記載されている流れの例です。 1つの`nginx`レプリカを含むDeployment(純粋にデモンストレーション目的です)とServiceがあるとします: From e58d996f3b5c2792dfb26b7a27c94074d743f4a9 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Wed, 22 Mar 2023 19:51:39 +0900 Subject: [PATCH 05/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: nasa9084 --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index 9facb8d43b..d0d87496fa 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -199,7 +199,7 @@ Podが削除される時には、古いエンドポイントも削除されま ## {{% heading "whatsnext" %}} -* [アプリケーションをサービスに接続する](/docs/tutorials/services/connect-applications-service/)方法を学びます。 +* [アプリケーションをServiceに接続する](/docs/tutorials/services/connect-applications-service/)方法を学びます。 * [Serviceを利用したクラスター内のアプリケーションへのアクセス](/docs/tasks/access-application-cluster/service-access-application-cluster/)を学びます。 * [Serviceを使用してフロントエンドをバックエンドに接続する](/docs/tasks/access-application-cluster/connecting-frontend-backend/)を学びます。 * [外部ロードバランサーの作成](/docs/tasks/access-application-cluster/create-external-load-balancer/)を学びます。 From e8593c75d28cc8a50190f603b5da38114162d324 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Mon, 27 Mar 2023 22:21:12 +0900 Subject: [PATCH 06/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: Toshiaki Inukai <82919057+t-inu@users.noreply.github.com> --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index d0d87496fa..786395dca8 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -8,7 +8,7 @@ weight: 60 [アプリケーションをServiceに接続する](/docs/tutorials/services/connect-applications-service/)で概略を示したステップに従ってアプリケーションをServiceに接続すると、ネットワーク上で公開され、継続的に実行されて、複製されたアプリケーションが得られます。 -このチュートリアルでは、Podを終了する流れを見て、graceful(上品)な接続ドレインを実装する手法を模索するための手助けをします。 +このチュートリアルでは、Podを終了する流れを見て、gracefulな(猶予のある)接続ドレインを実装する手法を模索するための手助けをします。 From 53a003eb311998e79510b244139c1cddd591365f Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Mon, 27 Mar 2023 22:25:34 +0900 Subject: [PATCH 07/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: Toshiaki Inukai <82919057+t-inu@users.noreply.github.com> --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index 786395dca8..0f25a97287 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -17,7 +17,7 @@ weight: 60 アップグレードやスケールダウンのために、Podを終了しなければならない場面はままあります。 アプリケーションの可用性を高めるために、適切なアクティブ接続ドレインを実装することは重要でしょう。 -このチュートリアルでは概念のデモンストレーションのために、シンプルなnginx Webサーバーを例として、関連付けられたエンドポイントステートに接続するPodの終了および削除の流れを説明します。 +このチュートリアルでは概念のデモンストレーションのために、シンプルなnginx Webサーバーを例として、対応するエンドポイントの状態に関連したPodの終了および削除の流れを説明します。 From 7fd3c30740e0e941f8a74ef494d4863bcd749558 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Mon, 27 Mar 2023 22:26:14 +0900 Subject: [PATCH 08/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: Toshiaki Inukai <82919057+t-inu@users.noreply.github.com> --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index 0f25a97287..c1dc8d227a 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -46,7 +46,7 @@ spec: labels: app: nginx spec: - terminationGracePeriodSeconds: 120 # 追加の長いgraceful期間 + terminationGracePeriodSeconds: 120 # 非常に長い猶予期間 containers: - name: nginx image: nginx:latest From 3995ff06a308c8f9139fcaedd2070a1c59930ccc Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Mon, 27 Mar 2023 22:26:26 +0900 Subject: [PATCH 09/12] Update content/ja/examples/service/pod-with-graceful-termination.yaml Co-authored-by: Toshiaki Inukai <82919057+t-inu@users.noreply.github.com> --- content/ja/examples/service/pod-with-graceful-termination.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/examples/service/pod-with-graceful-termination.yaml b/content/ja/examples/service/pod-with-graceful-termination.yaml index 395a53f5bd..cac714fa79 100644 --- a/content/ja/examples/service/pod-with-graceful-termination.yaml +++ b/content/ja/examples/service/pod-with-graceful-termination.yaml @@ -14,7 +14,7 @@ spec: labels: app: nginx spec: - terminationGracePeriodSeconds: 120 # 追加の長いgraceful期間 + terminationGracePeriodSeconds: 120 # 非常に長い猶予期間 containers: - name: nginx image: nginx:latest From 6de05754cf475a0c3fe0e430c4a00b793a1be2f4 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Mon, 27 Mar 2023 22:26:59 +0900 Subject: [PATCH 10/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: Toshiaki Inukai <82919057+t-inu@users.noreply.github.com> --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index c1dc8d227a..f4cbf1dd7c 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -78,7 +78,7 @@ spec: targetPort: 80 ``` -PodとServiceが実行中になったら、関連付けられたEndpointSlicesの名前を得られます: +PodとServiceが実行中になったら、関連付けられたEndpointSliceの名前を得られます: ```shell kubectl get endpointslice From 0d989413ba41525b2a4ae9ee2a79779e99b62e5e Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Tue, 28 Mar 2023 18:31:26 +0900 Subject: [PATCH 11/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: atoato88 --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index f4cbf1dd7c..85c94f3140 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -200,6 +200,6 @@ Podが削除される時には、古いエンドポイントも削除されま * [アプリケーションをServiceに接続する](/docs/tutorials/services/connect-applications-service/)方法を学びます。 -* [Serviceを利用したクラスター内のアプリケーションへのアクセス](/docs/tasks/access-application-cluster/service-access-application-cluster/)を学びます。 +* [Serviceを利用したクラスター内のアプリケーションへのアクセス](/ja/docs/tasks/access-application-cluster/service-access-application-cluster/)を学びます。 * [Serviceを使用してフロントエンドをバックエンドに接続する](/docs/tasks/access-application-cluster/connecting-frontend-backend/)を学びます。 * [外部ロードバランサーの作成](/docs/tasks/access-application-cluster/create-external-load-balancer/)を学びます。 From 40d4a10ef8f255e4500cd20b89781ea329dabe14 Mon Sep 17 00:00:00 2001 From: Kenshi Muto Date: Tue, 28 Mar 2023 18:32:00 +0900 Subject: [PATCH 12/12] Update content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md Co-authored-by: atoato88 --- .../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md index 85c94f3140..dfd102e025 100644 --- a/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md +++ b/content/ja/docs/tutorials/services/pods-and-endpoint-termination-flow.md @@ -201,5 +201,5 @@ Podが削除される時には、古いエンドポイントも削除されま * [アプリケーションをServiceに接続する](/docs/tutorials/services/connect-applications-service/)方法を学びます。 * [Serviceを利用したクラスター内のアプリケーションへのアクセス](/ja/docs/tasks/access-application-cluster/service-access-application-cluster/)を学びます。 -* [Serviceを使用してフロントエンドをバックエンドに接続する](/docs/tasks/access-application-cluster/connecting-frontend-backend/)を学びます。 +* [Serviceを使用してフロントエンドをバックエンドに接続する](/ja/docs/tasks/access-application-cluster/connecting-frontend-backend/)を学びます。 * [外部ロードバランサーの作成](/docs/tasks/access-application-cluster/create-external-load-balancer/)を学びます。