Update limits for pods to account for higher requirements

More RAM is needed to successfully start and have room to cache entries
with current load out. While the services can start with 256 in most
cases, it tends to be tight with some minor risk of OOM.

src/main/k8s/production.yml

@@ -36,11 +36,11 @@ spec:
         - containerPort: 8090
         resources:
           limits:
-            cpu: '1'
-            memory: 256Mi
+            cpu: 300m
+            memory: 384Mi
           requests:
-            cpu: 200m
-            memory: 128Mi
+            cpu: 300m
+            memory: 384Mi
         volumeMounts:
         - name: adopters
           mountPath: "/config"

src/main/k8s/staging.yml

@@ -36,11 +36,11 @@ spec:
         - containerPort: 8090
         resources:
           limits:
-            cpu: 200m
-            memory: 256Mi
+            cpu: 300m
+            memory: 384Mi
           requests:
-            cpu: 200m
-            memory: 256Mi
+            cpu: 300m
+            memory: 384Mi
         volumeMounts:
         - name: adopters
           mountPath: "/config"
@@ -78,7 +78,7 @@ metadata:
     haproxy.router.openshift.io/disable_cookies: "true"
     haproxy.router.openshift.io/balance: roundrobin
 spec:
-  host: "api.eclipse.org"
+  host: "api-staging.eclipse.org"
   path: "/adopters"
   port:
     targetPort: "http"