在合并前为流水线设门禁
先测量问题。在部署流水线中接入回滚步骤，当部署后健康检查超过重试阈值仍失败时触发回滚。 最常见的错误是未确认门禁能捕获你关心的问题就先加上。在接入 CI 之前，先对当前代码库运行 kubectl rollout undo deployment/api –to-revision=$(kubectl rollout history deployment/api | tail -2 | head -1 | awk ‘{print $1}’) 并检查输出。
kubectl rollout undo deployment/api --to-revision=$(kubectl rollout history deployment/api | tail -2 | head -1 | awk '{print $1}')让失败可操作
门禁就位后，让失败可操作。kubectl rollout undo deployment/api –to-revision=$(kubectl rollout history deployment/api | tail -2 | head -1 | awk ‘{print $1}’) 失败时应指向具体文件和行号，而非泛泛的错误。在锁文件中固定工具版本，防止上游发布悄悄改变行为。每次拉取请求都应像审查测试结果一样审查门禁输出。
验证
在本地运行 kubectl rollout undo deployment/api –to-revision=$(kubectl rollout history deployment/api | tail -2 | head -1 | awk ‘{print $1}’) 确认通过后推送。CI 中门禁应阻断不合规的拉取请求。若人为绕过门禁直接推送，应在下次定期扫描中被发现。
注意事项
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.