pgData Volume Auto-Grow KUTTL test

Adds a simple KUTTL E2E test for the pgData volume auto-grow feature.
This test performs one volume expansion and verifies the appropriate
annotation was set and Event was triggered.

Issue: PGO-1282

Author: tjmoore4

testing/kuttl/e2e-other/autogrow-volume/00-assert.yaml

@@ -0,0 +1,7 @@
+# Ensure that the default StorageClass supports VolumeExpansion
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  annotations:
+    storageclass.kubernetes.io/is-default-class: "true"
+allowVolumeExpansion: true

testing/kuttl/e2e-other/autogrow-volume/01-create.yaml

@@ -0,0 +1,6 @@
+apiVersion: kuttl.dev/v1beta1
+kind: TestStep
+apply:
+- files/01-create-cluster.yaml
+assert:
+- files/01-cluster-and-pvc-created.yaml

testing/kuttl/e2e-other/autogrow-volume/02-add-data.yaml

@@ -0,0 +1,6 @@
+apiVersion: kuttl.dev/v1beta1
+kind: TestStep
+apply:
+- files/02-create-data.yaml
+assert:
+- files/02-create-data-completed.yaml

testing/kuttl/e2e-other/autogrow-volume/03-assert.yaml

@@ -0,0 +1,12 @@
+---
+# Check that annotation is set
+apiVersion: v1
+kind: Pod
+metadata:
+  labels:
+    postgres-operator.crunchydata.com/cluster: auto-grow-volume
+    postgres-operator.crunchydata.com/data: postgres
+    postgres-operator.crunchydata.com/instance-set: instance1
+    postgres-operator.crunchydata.com/patroni: auto-grow-volume-ha
+  annotations:
+    suggested-pgdata-pvc-size: 1461Mi

testing/kuttl/e2e-other/autogrow-volume/04-assert.yaml

@@ -0,0 +1,19 @@
+# We know that the PVC sizes have changed so now we can check that they have been
+# updated to have the expected size
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  labels:
+    postgres-operator.crunchydata.com/cluster: auto-grow-volume
+    postgres-operator.crunchydata.com/instance-set: instance1
+spec:
+  resources:
+    requests:
+      storage: 1461Mi
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 2Gi
+  phase: Bound

testing/kuttl/e2e-other/autogrow-volume/05-check-event.yaml

@@ -0,0 +1,12 @@
+---
+apiVersion: kuttl.dev/v1beta1
+kind: TestStep
+commands:
+  # Verify expected event has occurred
+  - script: |
+      EVENT=$(
+        kubectl get events --namespace="${NAMESPACE}" \
+          --field-selector reason="VolumeAutoGrow" --output=jsonpath={.items..message}
+      )
+
+      if [[ "${EVENT}" != "pgData volume expansion to 1461Mi requested for auto-grow-volume/instance1." ]]; then exit 1; fi

testing/kuttl/e2e-other/autogrow-volume/README.md

@@ -0,0 +1,9 @@
+### AutoGrow Volume
+
+* 00: Assert the storage class allows volume expansion
+* 01: Create and verify PostgresCluster and PVC
+* 02: Add data to trigger growth and verify Job completes
+* 03: Verify annotation on the instance Pod
+* 04: Verify the PVC request has been set and the PVC has grown
+* 05: Verify the expansion request Event has been created
+      Note: This Event should be created between steps 03 and 04 but is checked at the end for timing purposes.

testing/kuttl/e2e-other/autogrow-volume/files/01-cluster-and-pvc-created.yaml

@@ -0,0 +1,27 @@
+apiVersion: postgres-operator.crunchydata.com/v1beta1
+kind: PostgresCluster
+metadata:
+  name: auto-grow-volume
+status:
+  instances:
+    - name: instance1
+      readyReplicas: 1
+      replicas: 1
+      updatedReplicas: 1
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  labels:
+    postgres-operator.crunchydata.com/cluster: auto-grow-volume
+    postgres-operator.crunchydata.com/instance-set: instance1
+spec:
+  resources:
+    requests:
+      storage: 1Gi
+status:
+  accessModes:
+  - ReadWriteOnce
+  capacity:
+    storage: 1Gi
+  phase: Bound

testing/kuttl/e2e-other/autogrow-volume/files/01-create-cluster.yaml

@@ -0,0 +1,27 @@
+apiVersion: postgres-operator.crunchydata.com/v1beta1
+kind: PostgresCluster
+metadata:
+  name: auto-grow-volume
+spec:
+  postgresVersion: ${KUTTL_PG_VERSION}
+  instances:
+    - name: instance1
+      dataVolumeClaimSpec:
+        accessModes:
+        - "ReadWriteOnce"
+        resources:
+          requests:
+            storage: 1Gi
+          limits:
+            storage: 2Gi
+  backups:
+    pgbackrest:
+      repos:
+      - name: repo1
+        volume:
+          volumeClaimSpec:
+            accessModes:
+            - "ReadWriteOnce"
+            resources:
+              requests:
+                storage: 1Gi

testing/kuttl/e2e-other/autogrow-volume/files/02-create-data-completed.yaml

@@ -0,0 +1,7 @@
+---
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: create-data
+status:
+  succeeded: 1

testing/kuttl/e2e-other/autogrow-volume/files/02-create-data.yaml

@@ -0,0 +1,32 @@
+---
+# Create some data that should be present after resizing.
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: create-data
+  labels: { postgres-operator-test: kuttl }
+spec:
+  backoffLimit: 3
+  template:
+    metadata:
+      labels: { postgres-operator-test: kuttl }
+    spec:
+      restartPolicy: Never
+      containers:
+        - name: psql
+          image: ${KUTTL_PSQL_IMAGE}
+          env:
+            - name: PGURI
+              valueFrom: { secretKeyRef: { name: auto-grow-volume-pguser-auto-grow-volume, key: uri } }
+
+            # Do not wait indefinitely, but leave enough time to create the data.
+            - { name: PGCONNECT_TIMEOUT, value: '60' }
+
+          command:
+            - psql
+            - $(PGURI)
+            - --set=ON_ERROR_STOP=1
+            - --command
+            - | # create schema for user and add enough data to get over 75% usage
+              CREATE SCHEMA "auto-grow-volume" AUTHORIZATION "auto-grow-volume";
+              CREATE TABLE big_table AS SELECT 'data' || s AS mydata FROM generate_series(1,6000000) AS s;