Tweak Kustomize resources: use different PVC storage class between UA…

…T and prod.

kustomize/base/deployment.yaml

@@ -3,7 +3,6 @@ kind: Deployment
 metadata:
   name: mapproxy-deployment
 spec:
-  replicas: 2
   strategy:
     type: RollingUpdate
   template:
@@ -17,8 +16,8 @@ spec:
           value: "Australia/Perth"
         resources:
           requests:
-            memory: "128Mi"
-            cpu: "10m"
+            memory: "200Mi"
+            cpu: "50m"
           limits:
             memory: "2Gi"
             cpu: "1000m"

kustomize/base/kustomization.yaml

@@ -2,5 +2,5 @@ apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 resources:
   - deployment.yaml
-  - pvc.yaml
+  - deployment_hpa.yaml
   - service.yaml

kustomize/overlays/prod/kustomization.yaml

@@ -5,6 +5,7 @@ resources:
   - ../../base
   - ingress.yaml
   - pdb.yaml
+  - pvc.yaml
 configMapGenerator:
   - name: mapproxy-configmap
     files:
@@ -15,6 +16,7 @@ labels:
       variant: prod
 patches:
   - path: deployment_patch.yaml
+  - path: deployment_hpa_patch.yaml
   - path: service_patch.yaml
 images:
   - name: ghcr.io/dbca-wa/mapproxy

kustomize/overlays/uat/kustomization.yaml

@@ -5,14 +5,16 @@ resources:
   - ../../base
   - ingress.yaml
   - pdb.yaml
+  - pvc.yaml
+configMapGenerator:
+  - name: mapproxy-configmap
+    files:
+      - mapproxy.yaml
 labels:
   - includeSelectors: true
     pairs:
       variant: uat
 patches:
   - path: deployment_patch.yaml
+  - path: deployment_hpa_patch.yaml
   - path: service_patch.yaml
-configMapGenerator:
-  - name: mapproxy-configmap
-    files:
-      - mapproxy.yaml

kustomize/overlays/uat/pvc.yaml

@@ -0,0 +1,12 @@
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: mapproxy-cache-data
+spec:
+  storageClassName: azurefile-csi-premium
+  volumeMode: Filesystem
+  accessModes:
+    - ReadWriteMany
+  resources:
+    requests:
+      storage: 32Gi