AKO Dry Run Mode
Parent: MongoDB Atlas Infrastructure as Code · Published reference · snapshot 2026-10-24 · skill mongodb-cohort-a634f98f5cef
↓ Facts as markdownall context files
Source-anchored research for AKO Dry Run Mode. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- Debug logging adds resource diffs for PUT/PATCH comparisons and extra Atlas GET requests; MongoDB recommends using debug logging in non-production because it increases load. (low confidence) [source]
Problems, failure modes and limitations
- Kubernetes API dry run with dryRun=All validates requests without persisting Kubernetes objects. AKO dry run requires actual Kubernetes resources and previews Atlas-side operations, so Kubernetes API validation alone cannot substitute for it. (high confidence) [source]
Comparisons and alternatives
- AKO dry run performs one reconciliation pass and exits rather than continuously reconciling. (high confidence) [source]
- A Kubernetes Job launches AKO with --dry-run. Reconciliation runs once rather than periodically; inspect emitted events with kubectl -n mongodb-atlas-system get events --field-selector reason=DryRun. (high confidence) [source]
- Inference from the v2.16.0 transport: a proposed Atlas mutation event does not prove Atlas would accept that request, because the transport returns a local DryRunError instead of sending the mutation. Treat it as an intent preview rather than an end-to-end execution guarantee. (high confidence) [source]
Facts and statements
- AKO dry run previews intended Atlas mutations without applying them. In v2.16.0, DryRunTransport forwards GET, CONNECT, TRACE and HEAD requests, but returns DryRunError for other methods; POST, PUT, PATCH and DELETE become proposed create, update or delete messages. (high confidence) [source]
- MongoDB's cached documentation snapshot labels AKO dry run public preview and warns that the feature and documentation may change during preview. (low confidence) (verified as of 2026-10-14) [source]
- For upgrade rehearsals, MongoDB instructs users to use a new Kubernetes/OpenShift cluster with target-version CRDs, custom resources, credential secrets, service account and RBAC. Replacing CRDs on the existing cluster may break reconciliation. (low confidence) [source]
- The Atlas CLI provides atlas kubernetes dry-run, with --operatorVersion, --targetNamespace, --watchNamespace, --watch and --watchTimeout. The documented procedure uses --watch to wait; without it, the CLI exits after installation. (high confidence) [source]
- In release 2.8.1, MongoDB fixed missing dry-run reporting for team-related operations. PR #2268 identifies swallowed errors for AtlasProject team associations; older output could omit intended actions. (high confidence) [source]
- Ariga's separately developed Atlas Kubernetes Operator documentation says its migration operator lacks dry run; that statement concerns AtlasMigration resources and does not contradict MongoDB AKO's documented dry-run capability. (high confidence) (verified as of 2026-10-23) [source]
Children
- No children recorded.