[codex] Support multi-pod application deployment - #3705
Closed
hhhhsc701 wants to merge 1 commit into
Closed
Conversation
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
hhhhsc701
force-pushed
the
dev/multi-pod-business
branch
from
August 19, 2026 06:50
09775b3 to
f04946a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The application services need to run with multiple replicas without losing run state, corrupting shared files, or routing resume/stop requests to the wrong pod.
Impact
Runtime state now depends on Redis in multi-pod deployments. Application charts default to three replicas and require shared RWX storage.
Validation
git diff --checkpassed.Stack
Base PR in the three-PR split. The Helm release split is stacked on this branch.