diff --git a/chart/templates/kiali/values.yaml b/chart/templates/kiali/values.yaml
index e8ead830ea368d49fc477d00a8a790e911197d83..199c5b9260a13754e7967d1607ce2056db9b18e1 100644
--- a/chart/templates/kiali/values.yaml
+++ b/chart/templates/kiali/values.yaml
@@ -35,6 +35,11 @@ cr:
       pod_annotations:
         {{ include "istioAnnotation" . }}
       {{- end }}
+      hpa:
+        spec:
+          maxReplicas: 2
+          minReplicas: 1
+          targetCPUUtilizationPercentage: 80
     server:
       web_port: "443"
     auth:
diff --git a/docs/developer/development-environment.md b/docs/developer/development-environment.md
index a03f78c219d09a065a797e06f6566b72a5573228..e60ad77552c1344163cbb40619c5cfcb025ee5c8 100644
--- a/docs/developer/development-environment.md
+++ b/docs/developer/development-environment.md
@@ -6,7 +6,7 @@ BigBang developers use [k3d](https://k3d.io/), a lightweight wrapper to run [k3s
 
 It is not recommend to run k3d with Big Bang on your local workstation. Instead use a remote k3d cluster running on an EC2 instance to shift the compute and network bandwidth to the cloud. Big Bang can be quite resource intensive and it requires a huge download bandwidth for the images. If you do insist on running k3d locally you should disable certain packages before deploying. You can do this in the values.yaml file by setting the package deploy to false. One of the packages that is most resource-intensive is the logging package. And you should create a local image registry cache to minimize the amount of image downloading.
 
-There is a script that automates the creation and teardown of a remote k3d development environment. First, read the [script instructions](aws-k3d-script.md), understand what it does, and install required dependencies. Then, run the script [docs/assets/developer/scripts/k3d-dev.sh](../assets/scripts/developer/k3d-dev.sh) from your workstation. The console output at the end of the script will give you the information necessary to access and use the dev environment. Also, there is a video tutorial in Platform One IL2 Confluence. Search for "T3" and click the link to the page. Scroll down the page to the 57th video on 22-February-2022.
+There is a script that automates the creation and teardown of a remote k3d development environment. First, read the [script instructions](aws-k3d-script.md), understand what it does, and install required dependencies. Then, run the script [docs/assets/scripts/developer/k3d-dev.sh](../assets/scripts/developer/k3d-dev.sh) from your workstation. The console output at the end of the script will give you the information necessary to access and use the dev environment. Also, there is a video tutorial in Platform One IL2 Confluence. Search for "T3" and click the link to the page. Scroll down the page to the 57th video on 22-February-2022.
 
 ## Prerequisites
 
diff --git a/docs/understanding-bigbang/package-architecture/kiali.md b/docs/understanding-bigbang/package-architecture/kiali.md
index 5332aada77a704e8c923d60fbb4d1bd66d8c48c9..77c738d58c235f36694f9012f4b47ea6b43770ef 100644
--- a/docs/understanding-bigbang/package-architecture/kiali.md
+++ b/docs/understanding-bigbang/package-architecture/kiali.md
@@ -92,7 +92,11 @@ monitoring:
 
 ## High Availability
 
-HA can be accomplished for Kiali via two methods. You can directly control the replicas required or have Kiali create and use a horizontal pod autoscaler and set a min/max number of replicas for the deployment. Both methods are shown below:
+HA can be accomplished for Kiali via two methods. You can directly control the replicas required or have Kiali create and use a horizontal pod autoscaler and set a min/max number of replicas for the deployment. 
+
+Big Bang uses the horizontal pod autoscaler by default with `minReplicas: 1` and `maxReplicas: 2`.  
+
+Both methods are shown below:
 
 - Specific number of replicas
 ```yaml