#translated-zh

CD Rollout Guard is a devops release control that limits exposure during gradual deployment for deployment automation and promotion. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.

CD Runbook Check is a devops operational test that confirms that documented procedures still work for deployment automation and promotion. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.

CD Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for deployment automation and promotion. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.

CD Trace Link is a devops observability link that connects a deployment or workflow to runtime evidence for deployment automation and promotion. It uses trace IDs, span metadata, and release identifiers so teams can debug production changes faster while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for content delivery and edge caching. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for content delivery and edge caching. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Egress Policy is a networking outbound control that decides where workloads may send traffic for content delivery and edge caching. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for content delivery and edge caching. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Health Probe is a networking availability check that tests whether a service or path can receive traffic for content delivery and edge caching. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Ingress Rule is a networking boundary rule that controls how external traffic enters a service for content delivery and edge caching. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Packet Capture is a networking diagnostic artifact that records network packets for analysis for content delivery and edge caching. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for content delivery and edge caching. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Rate Limit is a networking traffic control that caps request volume over a period for content delivery and edge caching. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for content delivery and edge caching. It uses TTL rules, cache keys, and invalidation so teams can reduce lookup latency while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for content delivery and edge caching. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.

CDN Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for content delivery and edge caching. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.

CI Approval Step is a devops workflow control that requires review before a sensitive change proceeds for continuous integration workflows. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.

CI Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for continuous integration workflows. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.

CI Build Gate is a devops quality gate that blocks promotion when required checks fail for continuous integration workflows. It uses tests, lint, security scans, and policy rules so teams can prevent broken releases while keeping evidence, reliability, and public-safe operational boundaries clear.

CI Config Drift Check is a devops consistency check that finds differences between intended and live configuration for continuous integration workflows. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.