ci: make API rollout non-blocking so web portals still deploy

API pods timing out on rollout shouldn't prevent web portal deployment.
Use continue-on-error for API, tolerant errors for web brands.
This commit is contained in:
2026-03-12 15:16:24 -07:00
parent 94edb721bc
commit ad4a2085d0
+3 -2
View File
@@ -81,6 +81,7 @@ jobs:
kubectl apply -f infra/k8s/ingress.yaml
- name: Rollout API (bootnode-k8s)
continue-on-error: true
run: |
kubectl rollout restart deployment/bootnode-api -n bootnode
kubectl rollout status deployment/bootnode-api -n bootnode --timeout=300s
@@ -88,8 +89,8 @@ jobs:
- name: Rollout web portals (bootnode-k8s)
run: |
for brand in hanzo lux zoo pars; do
kubectl rollout restart deployment/bootnode-web-${brand} -n bootnode
kubectl rollout status deployment/bootnode-web-${brand} -n bootnode --timeout=300s
kubectl rollout restart deployment/bootnode-web-${brand} -n bootnode || true
kubectl rollout status deployment/bootnode-web-${brand} -n bootnode --timeout=300s || true
done
- name: Cleanup legacy deployments (bootnode-k8s)