Skip to content

Commit ac51803

Browse files
authored
update to add references to EKS Auto Mode (#657)
1 parent f02a957 commit ac51803

File tree

4 files changed

+90
-311
lines changed

4 files changed

+90
-311
lines changed

latest/bpg/autoscaling/index.adoc

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,16 +15,15 @@
1515
:info_titleabbrev: Cluster Autoscaling
1616
:imagesdir: images/
1717

18-
This guide provides advice about Cluster Autoscaling, including guidance for Kubernetes Cluster Autoscaler and Karpenter.
18+
This guide provides advice about Cluster Autoscaling, including guidance for Auto Mode, Karpenter and Kubernetes Cluster Autoscaler.
1919

2020
[.topiclist]
2121
[[Topic List]]
2222

2323

24+
include::auto-mode.adoc[leveloffset=+1]
2425

2526
include::karpenter.adoc[leveloffset=+1]
2627

2728
include::cluster-autoscaler.adoc[leveloffset=+1]
2829

29-
include::auto-mode.adoc[leveloffset=+1]
30-

latest/bpg/reliability/application.adoc

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,16 @@ the current state with the desired state].
2525

2626
== Recommendations
2727

28+
=== Configure Pod Disruption Budgets
29+
30+
https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Pod Disruption Budgets] are
31+
used to limit the amount of concurrent disruption that an
32+
application will experience. They should be configured for workloads if its important to
33+
always have a portion of that workload available. EKS Auto Mode, Karpenter, and Cluster Autoscaler
34+
are aware of and adhere to configured Pod Disruption Budgets when scaling down.
35+
EKS Auto Mode, Karpenter and Managed Node Groups also adhere to Pod Disruption
36+
Budgets when updating Nodes
37+
2838
=== Avoid running singleton Pods
2939

3040
If your entire application runs in a single Pod, then your application

0 commit comments

Comments
 (0)