fix(chaos): harden k8s backend — supervise port-forward, guard fixture dir - #2346
Open
akshaychitneni wants to merge 1 commit into
Open
fix(chaos): harden k8s backend — supervise port-forward, guard fixture dir#2346akshaychitneni wants to merge 1 commit into
akshaychitneni wants to merge 1 commit into
Conversation
…e dir Follow-ups from apache#2244 (closes apache#2302): - Supervise the scheduler kubectl port-forward: a background task restarts it on exit and captures its stderr for dump_diagnostics, so a scheduler-pod restart or a transient apiserver/idle drop self-heals instead of leaving a permanently dead relay. - Guard CHAOS_FIXTURE_DIR before clearing it: refuse '/' or $HOME, and any non-empty directory the harness did not create (marker file), so a stray env var cannot turn the clear into a recursive delete.
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
1 participant
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.
Follow-ups from #2244:
Which issue does this PR close?
Closes #. #2302
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?