Skip to content

Commit f0ad66d

Browse files
committed
Grammar: 44303
1 parent 40baf39 commit f0ad66d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

latest/ug/clusters/zone-shift.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,11 @@ image::images/zs-traffic-flow-before-2.png[Illustration of network traffic]
2424
. The network packets are then sent to the Products Pod in AZ 2 via the ENIs on the respective nodes (as depicted in the diagram above).
2525

2626

27-
=== Understanding ARC Zonal Shift in EKS
27+
=== Understanding ARC Zonal Shift in Amazon EKS
2828

2929
In the case that there is an AZ impairment in your environment, you can initiate a zonal shift for your EKS cluster environment. Alternatively, you can allow {aws} to manage this for you with zonal autoshift. With zonal autoshift, {aws} will monitor the overall AZ health and respond to a potential AZ impairment by automatically shifting traffic away from the impaired AZ in your cluster environment.
3030

31-
Once your EKS cluster zonal shift enabled with ARC, you can trigger a zonal shift or enable zonal autoshift using the ARC Console, the {aws} CLI, or the zonal shift and zonal autoshift APIs.
31+
Once your Amazon EKS cluster has zonal shift enabled with ARC, you can trigger a zonal shift or enable zonal autoshift using the ARC Console, the {aws} CLI, or the zonal shift and zonal autoshift APIs.
3232
During an EKS zonal shift, the following will automatically take place:
3333

3434
* All the nodes in the impacted AZ will be cordoned. This will prevent the Kubernetes Scheduler from scheduling new Pods onto the nodes in the unhealthy AZ.

0 commit comments

Comments
 (0)