fix: try to address the CI failure

Signed-off-by: wuhuizuo <wuhuizuo@126.com>
PingCAP-QE · Sep 10, 2024 · becc5f2 · becc5f2
1 parent 63c1e7a
commit becc5f2
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 12 deletions.
diff --git a/charts/prow/templates/components/tide/deployment.yaml b/charts/prow/templates/components/tide/deployment.yaml
@@ -90,17 +90,17 @@ spec:
             httpGet:
               path: /healthz
               port: http
-            timeoutSeconds: 5
-            periodSeconds: 20
             failureThreshold: 3
-            initialDelaySeconds: 300
+            initialDelaySeconds: 30 # "300" maybe it will cause ci failed.
+            periodSeconds: 20
+            timeoutSeconds: 5
           readinessProbe:
             httpGet:
               path: /healthz/ready
               port: http
-            timeoutSeconds: 5
-            periodSeconds: 10
             failureThreshold: 3
+            periodSeconds: 10
+            timeoutSeconds: 5
           resources:
             {{- toYaml .Values.tide.resources | nindent 12 }}
       volumes:

diff --git a/charts/prow/values.yaml b/charts/prow/values.yaml
@@ -392,13 +392,13 @@ tide:
     roleBinding:
       create: true
       name: ""
-  resources:
-    requests:
-      cpu: 1000m
-      memory: 4Gi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
+  resources: {}
+    # requests:
+    #   cpu: 1000m
+    #   memory: 4Gi
+    # limits:
+    #   cpu: 1000m
+    #   memory: 4Gi
   kubeconfigSecret: ""
 
 pipeline: