← All documentation

Gateway checks

The integration guide explains the configured direct agent, gateway readiness signal, direct downstream and proxied A2A path. Replace the local endpoints with your deployment addresses. No servers are started by this example; functional probes require explicit safe configuration.

Phase 10 compatibility

This nested example remains valid. To share a backend across paths, give that node an explicit id and use ref edges. Each communication path keeps a distinct node and its own checks; edge policy remains independent. See the graph example. Graph fields require v0.8.0 or newer; v0.7.0 binaries reject them.

Kubernetes compatibility

Replace localhost with your in-cluster addresses when mounting this configuration. Gateway and routed peer checks retain separate evidence; the Kubernetes fixture is not product certification. See deployment scenarios and the deployment guide.

version: v1
targets:
  - name: direct-agent
    type: agent
    endpoint: http://localhost:8080/health
    dependencies:
      - name: agentgateway-readiness
        type: gateway
        endpoint: http://localhost:15021/healthz/ready
        http:
          expected_status: [200]
        dependencies:
          - name: downstream-direct
            type: a2a
            endpoint: http://localhost:9090
          - name: downstream-via-gateway
            type: a2a
            endpoint: http://localhost:3000