Package Management and Patch Strategy
On this page
Patching Strategy (Production)
- Patch windows + staged rollout (canary → small batch → fleet).
- Pin critical packages if needed; avoid surprise major upgrades.
- Always have rollback path (snapshot/AMI/image, version pin).
Inventory and Audit
# Debian/Ubuntu apt-cache policy <pkg> dpkg -l | head # RHEL/CentOS/Rocky rpm -qa | head dnf history | head
Safe Upgrade Flow
- Read release notes for kernel/libc/openssl changes.
- Upgrade on one node, validate service SLO signals, then proceed.
# Debian/Ubuntu apt-get update apt-get -s upgrade | head -200 # simulate apt-get upgrade -y
Hold/Pin (When Necessary)
# Debian/Ubuntu apt-mark hold openssl apt-mark unhold openssl
Failure Modes
- Kernel update: requires reboot; coordinate and drain traffic.
- Library bump: service crash due to ABI; rollback package version.
- Repo drift: mirrored repos out of sync; use internal repos for stability.