What is Drift-Erkennung?
In this glossary, Drift-Erkennung refers to: The automated process of identifying differences between the actual state of infrastructure and its intended, declarative configuration as defined in code or templates.
How is Drift-Erkennung used in IT and DevOps?
In IT and DevOps communication, this term appears in contexts such as: "Die Drift-Erkennung warnt Administratoren vor unautorisierten Änderungen an verwalteten Cloud-Ressourcen."
Why does Drift-Erkennung matter in IT and DevOps?
Drift-Erkennung matters because it supports clear communication in Infrastructure as Code contexts for DevOps Engineers, SREs, and Platform Engineers. It also connects to aviation training and exam language such as AWS Certification, Azure Certification, ITIL v4, and CKA/CKAD.
Who uses Drift-Erkennung?
Drift-Erkennung is mainly used by DevOps Engineers, SREs, and Platform Engineers.
What category does Drift-Erkennung belong to?
In this glossary, Drift-Erkennung is grouped under Infrastructure as Code. Related pages in this category explain adjacent procedures, commands and operational concepts.
Where does this definition come from?
This definition is sourced from ITIL v4, AWS Well-Architected Framework, Kubernetes Documentation, CNCF and published by Protermify IT/DevOps as a static IT and DevOps reference page.
