Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
Brouillon de traduction automatique (French) for "Observability Config Drift Check": Observability Config Drift Check is a devops consistency check that finds differences between intended and live configuration for logs, metrics, traces, and events. 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.
“Exemple en brouillon: The DevOps team used Observability Config Drift Check when latency increased after deploy, so the team could avoid surprise environment behavior before the deployment window opened.”
Brouillon de traduction automatique (French) for "Scheduler Autoscaling Policy": Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”
Brouillon de traduction automatique (French) for "Storage Workload Priority": Storage Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for persistent data and object access. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Storage Workload Priority when the workload read a large dataset, so the team could protect critical paths before the workload scaled up.”
Brouillon de traduction automatique (French) for "Secret Artifact Signature": Secret Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for credential and sensitive configuration. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Secret Artifact Signature when a token rotated, so the team could trust deployed packages before the deployment window opened.”
Brouillon de traduction automatique (French) for "Cluster Resource Quota": Cluster Resource Quota is a compute limit that sets how much compute a workload may consume for group of machines acting as one platform. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Cluster Resource Quota when the cluster added a node pool, so the team could protect shared capacity before the workload scaled up.”
Brouillon de traduction automatique (French) for "Incident Rollout Guard": Incident Rollout Guard is a devops release control that limits exposure during gradual deployment for response to service degradation. 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.
“Exemple en brouillon: The DevOps team used Incident Rollout Guard when on-call received a high-severity page, so the team could reduce blast radius before the deployment window opened.”
Brouillon de traduction automatique (French) for "BGP Ingress Rule": BGP Ingress Rule is a networking boundary rule that controls how external traffic enters a service for interdomain routing. 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.
“Exemple en brouillon: The network engineering team used BGP Ingress Rule when a route advertisement changed, so the team could keep entry points predictable before traffic crossed a service boundary.”
Brouillon de traduction automatique (French) for "Secret Approval Step": Secret Approval Step is a devops workflow control that requires review before a sensitive change proceeds for credential and sensitive configuration. 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.
“Exemple en brouillon: The DevOps team used Secret Approval Step when a token rotated, so the team could keep high-risk automation accountable before the deployment window opened.”
Brouillon de traduction automatique (French) for "Infrastructure Secret Rotation": Infrastructure Secret Rotation is a devops credential workflow that replaces sensitive keys without service interruption for cloud resources and platform wiring. It uses dual credentials, rollout steps, and revocation so teams can reduce credential exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The DevOps team used Infrastructure Secret Rotation when a new region was added, so the team could reduce credential exposure before the deployment window opened.”
Brouillon de traduction automatique (French) for "Container Autoscaling Policy": Container Autoscaling Policy is a compute control loop that changes capacity based on demand signals for packaged application runtime. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemple en brouillon: The platform engineering team used Container Autoscaling Policy when the image started on a new node, so the team could match resources to load before the workload scaled up.”