Remove rollout status check (too many open files in CI)
All checks were successful
ci/woodpecker/push/build Pipeline was successful
All checks were successful
ci/woodpecker/push/build Pipeline was successful
Rollout restart is enough — status monitoring is optional and fails with fsnotify watcher limit in the CI pod. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -42,4 +42,3 @@ steps:
|
|||||||
- kubectl config set-context deploy --cluster=k3s --user=deployer --namespace=bbb
|
- kubectl config set-context deploy --cluster=k3s --user=deployer --namespace=bbb
|
||||||
- kubectl config use-context deploy
|
- kubectl config use-context deploy
|
||||||
- kubectl rollout restart deploy/bbb-backend deploy/bbb-frontend -n bbb
|
- kubectl rollout restart deploy/bbb-backend deploy/bbb-frontend -n bbb
|
||||||
- kubectl rollout status deploy/bbb-backend deploy/bbb-frontend -n bbb --timeout=120s
|
|
||||||
|
|||||||
Reference in New Issue
Block a user