# Readiness Gate - CI/CD用語集の定義

> Readiness Gate: readiness gateとは、インスタンスまたはdeploymentがトラフィックを受け取る準備が整ったとみなされる前に満たされる必要がある条件であり、

Source: https://latchkey.dev/ja/learn/ci-glossary/readiness-gate-gl20  
Updated: 2026-06-30

readiness gateは、必須の条件が満たされるまでインスタンスをローテーションから外しておきます。

基本的なreadiness probeを超えて、readiness gateはトラフィックがルーティングされる前に外部の状態（load balancerがインスタンスを登録するなど）を要求できます。これにより、まだ準備が整っていないターゲットへ負荷を移すことを防ぎます。

## Where this shows up in a real pipeline

A definition is only useful if you can recognise the thing in your own logs. In practice this concept surfaces when a job behaves differently between a local run and a runner, which is where most CI debugging starts.

- Compare a local run against a CI run of the same command before assuming a tool is at fault.
- Runner environments differ in shell, PATH, TTY availability, available memory, and disk. Most CI-only behaviour traces to one of those five.
- Pin tool versions so an environment difference cannot be introduced by an unrelated update.

## FAQ

### What is Readiness gate?

A readiness gate is a condition that must be satisfied before an instance or deployment is considered ready to receive traffic, letting a rollout wait on external signals.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt