Dry run
A dry run is an execution mode that previews, validates, or reports an operation’s prospective behavior without carrying out the effects being previewed.
Google Anthos in Action
Dry-run is an enforcement mode that reports policy violations without blocking the operation that caused them.
- How it is used
- Tests Policy Controller constraints against a cluster before enforcement can disrupt Pods.
- How deep it goes
- Walks through manifest configuration, violation inspection, and promotion to enforcement, without detailing the audit controller's internals.
- Examples
- Uses privileged-container and host-namespace constraint manifests, plus audit output identifying affected system Pods.
- What you can do after
- Operate/configure it to identify unintended policy violations before changing a constraint to enforcement.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A dry run is an execution mode that analyzes and reports expected changes without applying them to the target resources.
- How it is used
- Uses infrastructure previews to review provisioning changes, test configuration, and protect live resources during refactoring or tool migration.
- How deep it goes
- Explains previews, dependencies, JSON inspection, testing, and refactoring checks, but leaves dry-run formats and standards broadly unspecified.
- Examples
- Uses Terraform plans, JSON dry-run files, pytest checks, subnet configurations, and no-change refactoring plans.
- What you can do after
- Diagnoses unintended infrastructure changes and validates configuration before deployment or migration.
Acing the Certified Kubernetes Administrator Exam, Second Edition
Dry-run is a command option that simulates an operation without applying its resulting resource changes.
- How it is used
- Generates Kubernetes resource skeletons for editing, verification, and efficient exam-oriented manifest creation.
- How deep it goes
- Explains client-side YAML generation and the subsequent creation step, but does not detail broader dry-run behavior.
- Examples
- Uses kubectl run to generate Pod YAML, edits tolerations or containers, and later creates or applies the manifest.
- What you can do after
- Build it from scratch by generating an editable Kubernetes manifest and applying it after the required fields are added.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains dry run →
Related concepts
- evidenceproduces · Evidence is information, observations, or material used to support, challenge, or assess a claim, conclusion, event, or outcome.
- misconfigurationaddresses · A misconfiguration is an incorrect, unsuitable, or insufficiently restrictive system or application setting that causes unintended behavior, operational problems, or security exposure.
- configurationuses · A specification of settings, parameters, or component relationships that determines how a system, application, model, or process is structured or operates.
- deployment pipelineused by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
- kubectl runused by · kubectl run is a Kubernetes command that creates a pod from a container image and command-line options.
- provisioning toolused by · Software that creates and prepares infrastructure resources and manages their infrastructure-level dependencies.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.