Remove nodeSelector from k8s deployments (#2798)

nodeSelector can limit scheduling capabilities of k8s, which leads to delays in assigning new workloads. Since we do not require and particular machine for execution it can be removed.

Author: ptkach

jetty/kubernetes/nomulus-backend.yaml

@@ -14,9 +14,6 @@ spec:
         service: backend
     spec:
       serviceAccountName: nomulus
-      nodeSelector:
-        cloud.google.com/compute-class: "Performance"
-        cloud.google.com/machine-family: c4
       containers:
       - name: backend
         image: gcr.io/GCP_PROJECT/nomulus
@@ -25,9 +22,15 @@ spec:
           name: http
         resources:
           requests:
+            # explicit pod-slots 0 is required in order to downgrade node
+            # class from performance, which has implicit pod-slots 1
+            cloud.google.com/pod-slots: 0
             cpu: "500m"
             memory: "1Gi"
           limits:
+            # explicit pod-slots 0 is required in order to downgrade node
+            # class from performance, which has implicit pod-slots 1
+            cloud.google.com/pod-slots: 0
             cpu: "1000m"
             memory: "1Gi"
         args: [ENVIRONMENT]

jetty/kubernetes/nomulus-frontend.yaml

@@ -14,9 +14,6 @@ spec:
         service: frontend
     spec:
       serviceAccountName: nomulus
-      nodeSelector:
-        cloud.google.com/compute-class: "Performance"
-        cloud.google.com/machine-family: c4
       containers:
       - name: frontend
         image: gcr.io/GCP_PROJECT/nomulus
@@ -25,9 +22,15 @@ spec:
           name: http
         resources:
           requests:
+            # explicit pod-slots 0 is required in order to downgrade node
+            # class from performance, which has implicit pod-slots 1
+            cloud.google.com/pod-slots: 0
             cpu: "1000m"
             memory: "1Gi"
           limits:
+            # explicit pod-slots 0 is required in order to downgrade node
+            # class from performance, which has implicit pod-slots 1
+            cloud.google.com/pod-slots: 0
             cpu: "1000m"
             memory: "2Gi"
         args: [ENVIRONMENT]
@@ -53,9 +56,15 @@ spec:
           name: epp
         resources:
           requests:
+            # explicit pod-slots 0 is required in order to downgrade node
+            # class from performance, which has implicit pod-slots 1
+            cloud.google.com/pod-slots: 0
             cpu: "1000m"
             memory: "512Mi"
           limits:
+            # explicit pod-slots 0 is required in order to downgrade node
+            # class from performance, which has implicit pod-slots 1
+            cloud.google.com/pod-slots: 0
             cpu: "1000m"
             memory: "512Mi"
         args: [--env, PROXY_ENV, --log, --local]