Repository navigation
fix(ci): recover stuck dev Elasticsearch rollout - #100
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 13, 2026
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
2 participants
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.
The corrected dev Elasticsearch template could not roll out because the existing single-replica
OrderedReadyStatefulSet pod was non-ready on the previous controller revision. The deployment now detects that exact state after applying the manifest and recreates only the non-ready, outdated pod, allowing Kubernetes to start the desired revision with the retained PVC.The recovery runs only from the dev GitHub Actions deployment paths. It does not delete a pod that is ready or already on the desired revision.
Validation:
bash deploy/k8s/tests/recover-stuck-statefulset.shbash -n deploy/k8s/scripts/recover-stuck-statefulset.sh deploy/k8s/tests/recover-stuck-statefulset.shgit diff --checkharness check scopeharness check branchExternal review note: AGY Gemini 3.8 was launched repeatedly with the complete diff but exited after initialization without returning a verdict; the interactive fallback stopped at its local trust prompt before submitting the brief.