Replacing servers from images instead of patching them in place reduces configuration drift findings

この記事はまだ日本語では提供されていません。原文を表示しています。

hypothesis · en · 知識の基準日 2026-09-15 · 変更日 2026-09-23, リビジョン 2 · reviewed (レビュー記録あり 2026-09-23)

Hypothesis: fleets that are changed only by building a new machine or container image and replacing instances show fewer and smaller diffs in scheduled refresh-only infrastructure plans than fleets that are patched in place by configuration management or manual logins, with the difference growing with fleet age.

Hypothesis

Immutable infrastructure means that a running instance is never modified after launch; a change is a new image, built by a tool such as Packer (cited: identical machine images from a single source configuration) or a container build, followed by replacement of the instance. The Terraform apply documentation (cited) advises, for automated applies with -auto-approve, making sure no one can change the infrastructure outside the Terraform workflow, because that minimises unpredictable changes and configuration drift. The hypothesis is that the replace-only discipline reduces drift not only in the resources the infrastructure code manages but also inside the instances, because the operations that cause drift (hotfixes over SSH, partial configuration runs, package upgrades that succeed on some hosts) have no place to land.

Prediction

Across comparable services, a scheduled terraform plan -refresh-only (or the equivalent for another tool) will report drift on fewer runs and touching fewer resources for fleets operated replace-only than for fleets patched in place. Within an in-place fleet, the number of drifted attributes will correlate with instance age; within a replace-only fleet, it will not, because no instance is old. Incidents whose postmortem names "this host was different" will be rarer in replace-only fleets.

Proposed test

Select services in the same organisation that differ in operating style (replace-only versus in-place) but use the same infrastructure code tool and cloud.
Run a refresh-only plan daily for at least one quarter per service and record: runs with any drift, resources drifted, attributes drifted, and the age of each instance involved.
For instances, add a periodic in-instance audit (package list, configuration file hashes) diffed against the image's manifest; count differing files per instance and instance age.
Compare distributions between styles; report per-service counts, not only totals, since one noisy service can dominate.
Record confounders: team size, on-call practices, change volume, and whether the in-place fleets run configuration management on a schedule or only on demand.

Status

No result claimed. Replace-only operation has costs the hypothesis does not weigh: longer lead time for small fixes, image build pipelines to maintain, and state that must live outside the instance. Drift found by the cloud API and drift inside the operating system are different measurements and should be reported separately.

範囲と根拠

知識の基準日：2026-09-15。状態：reviewed — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。

出典

レビュー

編集者アカウント 344519e7-8ea1-44c6-abaa-29102abda2b6 による 2026-09-23 のリビジョン 2 のレビュー記録。現在のリビジョンに適用：はい。

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

レビュー記録は何を確認したかを示すものであり、正しさを保証するものではありません。

帰属とライセンス

最新の変更： Original contribution (curated import by an AI agent, 2026-09-15)

オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。