Skip to content

feat(helm): update chart external-secrets (2.8.0 → 2.11.0) - #3794

Open
bot-akira[bot] wants to merge 1 commit into
mainfrom
renovate/external-secrets-2.x
Open

bot-akira[bot] wants to merge 1 commit into
mainfrom
renovate/external-secrets-2.x

Conversation

@bot-akira

@bot-akira bot-akira Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
external-secrets minor 2.8.02.11.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

external-secrets/external-secrets (external-secrets)

v2.11.0

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v2.11.0
Image: ghcr.io/external-secrets/external-secrets:v2.11.0-ubi
Image: ghcr.io/external-secrets/external-secrets:v2.11.0-ubi-boringssl

What's Changed

General
Dependencies

New Contributors

Full Changelog: external-secrets/external-secrets@v2.10.0...v2.11.0

v2.10.0

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v2.10.0
Image: ghcr.io/external-secrets/external-secrets:v2.10.0-ubi
Image: ghcr.io/external-secrets/external-secrets:v2.10.0-ubi-boringssl

What's Changed

General
Dependencies

New Contributors

Full Changelog: external-secrets/external-secrets@v2.9.0...v2.10.0

v2.9.0

Compare Source

Image: ghcr.io/external-secrets/external-secrets:v2.9.0
Image: ghcr.io/external-secrets/external-secrets:v2.9.0-ubi
Image: ghcr.io/external-secrets/external-secrets:v2.9.0-ubi-boringssl

What's Changed

General
Dependencies

New Contributors

Full Changelog: external-secrets/external-secrets@v2.8.0...v2.9.0


Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@bot-akira

bot-akira Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

Note

18 resources changed across 2 apps · 14 CRDs

Blast radius

  • Kustomization kube-system/external-secrets: 15 dependents (kube-system/external-secrets-stores +14 more)
image from to upstream
ghcr.io/external-secrets/external-secrets v2.8.0 v2.11.0

konflate 0.6.4 · rendered ac6c254 · full diff →

@bot-akira bot-akira Bot added the auto-merge label Aug 20, 2026
@bot-akira
bot-akira Bot force-pushed the renovate/external-secrets-2.x branch from c3f06f3 to e2462c7 Compare August 28, 2026 19:45
@bot-akira bot-akira Bot changed the title feat(helm): update chart external-secrets (2.8.0 → 2.9.0) feat(helm): update chart external-secrets (2.8.0 → 2.10.0) Aug 28, 2026
@axeII

axeII commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Do not merge yet — this reintroduces a known crash.

We hit this exact chart version before: #3793 reverted external-secrets 2.9.0 → 2.8.0 on 2026-08-20 after all 37 ExternalSecrets in the cluster failed to sync with:

could not get secret data from provider: wasm error: out of bounds memory access
op_extism_core.wasm ... extism_pdk::input_bytes

Root cause: the onepasswordSDK provider's WASM plugin (Extism) crashing on every fetch. This cluster uses onepasswordSDK (stores/onepassword/clustersecretstore.yaml), so it's directly exposed.

Confirmed via go.mod across tags — the dependency bump that caused it has not moved since:

Chart version 1Password/onepassword-sdk-go
2.8.0 (known-good) v0.3.1
2.9.0 (crashed, reverted in #3793) v0.4.1
2.10.0 (this PR) v0.4.1 — unchanged
upstream main (current tip) v0.4.1 — still unchanged

Nothing in the 2.9.0→2.10.0 changelog touches the 1Password SDK WASM invocation path (#6318/#6782 only add a mutually-exclusive environment field, which doesn't affect our vault-only config). No upstream issue exists yet for this crash string in either external-secrets/external-secrets or 1Password/onepassword-sdk-go — it looks unreported.

Because deletionPolicy: Retain keeps existing target Secrets serving their last-good values, a repeat of this wouldn't be immediately visible — it would just silently block all secret rotation and new ExternalSecrets again.

Hold until onepassword-sdk-go moves past v0.4.1 upstream (or the crash gets root-caused another way). Leaving needs-review/do not merge in place.

Signed-off-by: bot-akira[bot] <159718293+bot-akira[bot]@users.noreply.github.com>
@bot-akira
bot-akira Bot force-pushed the renovate/external-secrets-2.x branch from e2462c7 to ac6c254 Compare September 21, 2026 17:22
@bot-akira bot-akira Bot changed the title feat(helm): update chart external-secrets (2.8.0 → 2.10.0) feat(helm): update chart external-secrets (2.8.0 → 2.11.0) Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant