Menu

When an `ExternalSecret` Runs on Backoff Behind a Late `SecretStore`
📰

When an `ExternalSecret` Runs on Backoff Behind a Late `SecretStore`

DEV Community: kubernetes·When It Runs·1 day ago
#LEiMrehX
#devtokubernetes#devto#dev#rr13#seconds
Reading 0:00
15s threshold

External Secrets Operator v2.11.0: with its SecretStore not ready, an ExternalSecret retried 1, 4, 8, 16, … seconds apart up to 7 minutes, not per refreshInterval , and synced at its next retry.

When It Runs — Run Report #RR13 · Testing what infrastructure actually does.

Provider · Component: External Secrets Operator · the first sync of an ExternalSecret whose SecretStore becomes ready late — when the controller retries the failed sync and when the Secret appears, with the flood gate on (its default)

Versions tested: measured — External Secrets Operator v2.11.0 (the current minor release as of 2026-09-28; v2.12.0, v2.13.0, v2.14.0 and v2.15.0, released on 2026-10-06, 2026-10-16, 2026-10-23 and 2026-11-10, were not measured, and v2.15.0 is the current minor release as of 2026-11-10; the project supports only the current minor version, and its support table lists 2.11's end of life as 2026-10-06), a single version.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.