fix deployments for backend and auth-service

deployment/auth-service/deployment.yaml

@@ -10,13 +10,11 @@ metadata:
   name: gh-auth-service
   namespace: generations-heritage
 spec:
-  podManagementPolicy: OrderedReady
   replicas: 1
   selector:
     matchLabels:
       app.kubernetes.io/instance: gh-auth-service
       app.kubernetes.io/name: gh-auth-service
-  serviceName: gh-auth-service
   template:
     metadata:
       labels:
@@ -39,12 +37,10 @@ spec:
             requests:
               cpu: 100m
               memory: 50Mi
-            volumeMounts:
-              - name: gh-auth-service-certs
-                mountPath: /etc/gh-auth-service/ssl
+          volumeMounts:
+            - name: gh-auth-service-certs
+              mountPath: /etc/gh-auth-service/ssl
       volumes:
       - name: gh-auth-service-certs
         secret:
           secretName: gh-auth-service-tls
-  updateStrategy:
-    type: RollingUpdate

deployment/backend/deployment.yaml

@@ -9,13 +9,11 @@ metadata:
     argocd.argoproj.io/hook: Synce
   name: gh-backend
 spec:
-  podManagementPolicy: OrderedReady
   replicas: 1
   selector:
     matchLabels:
       app.kubernetes.io/instance: gh-backend
       app.kubernetes.io/name: gh-backend
-  serviceName: gh-backend
   template:
     metadata:
       labels:
@@ -38,11 +36,10 @@ spec:
             requests:
               cpu: 100m
               memory: 100Mi
-            volumeMounts:
-              - name: gh-backend-certs
-                mountPath: /etc/gh-backend/ssl
+          volumeMounts:
+            - name: gh-backend-certs
+              mountPath: /etc/gh-backend/ssl
       volumes:
       - name: gh-backend-certs
         secret:
           secretName: gh-backend-tls
-