autoscaling all done

Signed-off-by: Hiranmoy Das Chowdhury <[email protected]>

docs/examples/pgbouncer/autoscaling/compute/pgbouncer-autoscale.yaml

@@ -0,0 +1,23 @@
+apiVersion: kubedb.com/v1
+kind: PgBouncer
+metadata:
+  name: pgbouncer-autoscale
+  namespace: demo
+spec:
+  replicas: 1
+  version: "1.18.0"
+  database:
+    syncUsers: true
+    databaseName: "postgres"
+    databaseRef:
+      name: "ha-postgres"
+      namespace: demo
+  connectionPool:
+    poolMode: session
+    port: 5432
+    reservePoolSize: 5
+    maxClientConnections: 87
+    defaultPoolSize: 2
+    minPoolSize: 1
+    authType: md5
+  deletionPolicy: WipeOut

docs/examples/pgbouncer/autoscaling/compute/pgbouncer-autoscaler.yaml

@@ -0,0 +1,21 @@
+apiVersion: autoscaling.kubedb.com/v1alpha1
+kind: PgBouncerAutoscaler
+metadata:
+  name: pgbouncer-autoscale-ops
+  namespace: demo
+spec:
+  databaseRef:
+    name: pgbouncer-autoscale
+  compute:
+    pgbouncer:
+      trigger: "On"
+      podLifeTimeThreshold: 5m
+      resourceDiffPercentage: 20
+      minAllowed:
+        cpu: 400m
+        memory: 400Mi
+      maxAllowed:
+        cpu: 1
+        memory: 1Gi
+      controlledResources: ["cpu", "memory"]
+      containerControlledValues: "RequestsAndLimits"

docs/guides/pgbouncer/autoscaler/compute/compute-autoscale.md

@@ -97,7 +97,6 @@ Let's check the Pod containers resources,
 $ kubectl get pod -n demo pgbouncer-autoscale-0 -o json | jq '.spec.containers[].resources'
 {
   "limits": {
-    "cpu": "200m",
     "memory": "300Mi"
   },
   "requests": {
@@ -112,7 +111,6 @@ Let's check the PgBouncer resources,
 $ kubectl get pgbouncer -n demo pgbouncer-autoscale -o json | jq '.spec.podTemplate.spec.containers[0].resources'
 {
   "limits": {
-    "cpu": "200m",
     "memory": "300Mi"
   },
   "requests": {
@@ -403,7 +401,6 @@ Now, we are going to verify from the Pod, and the PgBouncer yaml whether the res
 $ kubectl get pod -n demo pgbouncer-autoscale-0 -o json | jq '.spec.containers[].resources'
 {
   "limits": {
-    "cpu": "400m",
     "memory": "400Mi"
   },
   "requests": {
@@ -415,7 +412,6 @@ $ kubectl get pod -n demo pgbouncer-autoscale-0 -o json | jq '.spec.containers[]
 $ kubectl get pgbouncer -n demo pgbouncer-autoscale -o json | jq '.spec.podTemplate.spec.containers[0].resources'
 {
   "limits": {
-    "cpu": "400m",
     "memory": "400Mi"
   },
   "requests": {

docs/guides/pgbouncer/autoscaler/compute/overview.md

@@ -28,7 +28,7 @@ This guide will give an overview on how KubeDB Autoscaler operator autoscales th
 The following diagram shows how KubeDB Autoscaler operator autoscales the resources of `PgBouncer`. Open the image in a new tab to see the enlarged version.
 
 <figure align="center">
-  <img alt="Compute Auto Scaling process of PgBouncer" src="/docs/images/day-2-operation/pgbouncer/compute-process.png">
+  <img alt="Compute Auto Scaling process of PgBouncer" src="/docs/images/day-2-operation/pgbouncer/autoscaling.png">
 <figcaption align="center">Fig: Compute Auto Scaling process of PgBouncer</figcaption>
 </figure>