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

Merge pull request #48763 from Thoughtscript/patch-2 

docs: typos
This commit is contained in:
Kubernetes Prow Robot 2024-11-20 15:52:54 +00:00 committed by GitHub
parent 966af4105e 6a73d0e087
commit 68ed21755d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/tutorials/services/connect-applications-service.md
View File

@ -90,7 +90,7 @@ kubectl expose deployment/my-nginx
service/my-nginx exposed service/my-nginx exposed
``` ```
This is equivalent to `kubectl apply -f` the following yaml: This is equivalent to `kubectl apply -f` in the following yaml:
{{% code_sample file="service/networking/nginx-svc.yaml" %}} {{% code_sample file="service/networking/nginx-svc.yaml" %}}

12
content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
View File

@ -17,7 +17,7 @@ graceful connection draining.
## Termination process for Pods and their endpoints ## 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. There are often cases when you need to terminate a Pod - be it to upgrade or scale down.
In order to improve application availability, it may be important to implement In order to improve application availability, it may be important to implement
a proper active connections draining. a proper active connections draining.
@ -29,12 +29,12 @@ a simple nginx web server to demonstrate the concept.
## Example flow with endpoint termination ## Example flow with endpoint termination
The following is the example of the flow described in the The following is the example flow described in the
[Termination of Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination) [Termination of Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)
document. document.
Let's say you have a Deployment containing of a single `nginx` replica Let's say you have a Deployment containing a single `nginx` replica
(just for demonstration purposes) and a Service: (say just for the sake of demonstration purposes) and a Service:
{{% code_sample file="service/pod-with-graceful-termination.yaml" %}} {{% code_sample file="service/pod-with-graceful-termination.yaml" %}}
@ -158,10 +158,10 @@ The output is similar to this:
``` ```
This allows applications to communicate their state during termination This allows applications to communicate their state during termination
and clients (such as load balancers) to implement a connections draining functionality. and clients (such as load balancers) to implement connection draining functionality.
These clients may detect terminating endpoints and implement a special logic for them. 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`. In Kubernetes, endpoints that are terminating always have their `ready` status set as `false`.
This needs to happen for backward This needs to happen for backward
compatibility, so existing load balancers will not use it for regular traffic. 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 If traffic draining on terminating pod is needed, the actual readiness can be