From c606d2a63383c119b9ab2881a260f0178367e236 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Suraj=20Banakar=28=E0=A4=AC=E0=A4=BE=E0=A4=A8=E0=A4=95?=
 =?UTF-8?q?=E0=A4=B0=29=20=7C=20=E3=82=B9=E3=83=A9=E3=82=B8?=
 <34534103+vadasambar@users.noreply.github.com>
Date: Mon, 6 Mar 2023 10:15:23 +0530
Subject: [PATCH] docs: add info about mirror pods

- because we use `mirror pods` in our flags but don't really talk about what they mean anywhere
---
 cluster-autoscaler/FAQ.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/cluster-autoscaler/FAQ.md b/cluster-autoscaler/FAQ.md
index 3d7316aefa43..913ac7944056 100644
--- a/cluster-autoscaler/FAQ.md
+++ b/cluster-autoscaler/FAQ.md
@@ -722,6 +722,9 @@ CA respects `nodeSelector` and `requiredDuringSchedulingIgnoredDuringExecution`
 
 However, CA does not consider "soft" constraints like `preferredDuringSchedulingIgnoredDuringExecution` when selecting node groups. That means that if CA has two or more node groups available for expansion, it will not use soft constraints to pick one node group over another.
 
+### What are mirror pods?
+Mirror pods are pods which are considered `replicated` i.e., if the node on which the pod is running goes down, the pod can get scheduled on another node.  
+
 ****************
 
 ### What are the parameters to CA?