Skip to content

feat(langsmith): add JuiceFS mount pod replacement [v16-stable] - #921

Closed
Daniel Kneipp (DanielKneipp) wants to merge 1 commit into
daniel/v16-unified-sandbox-juicefs-imagefrom
daniel/v16-juicefs-mount-pod-replacement
Closed

feat(langsmith): add JuiceFS mount pod replacement [v16-stable]#921
Daniel Kneipp (DanielKneipp) wants to merge 1 commit into
daniel/v16-unified-sandbox-juicefs-imagefrom
daniel/v16-juicefs-mount-pod-replacement

Conversation

@DanielKneipp

@DanielKneipp Daniel Kneipp (DanielKneipp) commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add an opt-in, one-shot JuiceFS mount-pod replacement flow for Helm upgrades
  • discover only mount pods for the configured sandbox volume and recreate each pod on its current node
  • require JuiceFS CE 1.2.1 or newer and explicit POD-SUCCESS output
  • track completed request IDs so repeated upgrades are idempotent
  • scope the temporary node pods/exec permission and completion marker update

This PR is intentionally stacked on #906 and contains only the mount-pod upgrade behavior, validation, tests, and documentation.

User impact

Normal Helm upgrades continue to leave existing JuiceFS mount pods untouched. An operator can set sandboxes.juicefs.csi.mountPodReplacementRequestId during a direct upgrade to request a coordinated replacement, then clear the value after completion.

Validation

  • helm unittest charts/langsmith (310 tests)
  • helm lint charts/langsmith --values charts/langsmith/tests/values/sandboxes-enabled.yaml
  • normal and upgrade-specific helm template renders
  • kubeconform -strict -summary -ignore-missing-schemas (180 resources, 0 invalid)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant