Scenario
A certificate rotates successfully in cluster state and the application continues presenting the old material until a restart.
A cert-manager renewal succeeds and the new certificate never reaches the app because the pod mounts the secret through subPath and therefore never sees the updated file
The Secret object changes, yet the running container still serves the old certificate because the mount mode broke live update propagation.
What to check first
- Identify the primary failure signal in the The Secret Rotated, the Mounted File Stayed Frozen scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Check mount style before changing renewal cadence or certificate issuer settings.
Questions worth viewing together
Community-field Kubernetes problem inspired by community cert-manager patterns where subPath-mounted Secrets never reflected renewed certificates. Secret rotation debugging should include how the file enters the container, not only whether the Secret updated.
Teams often blame cert-manager when the pod never had a refresh-capable mount pattern.
subPath mounts trade convenience for losing many live-update semantics.
Similar cases seen in the field