Fix network policy: allow Redis Sentinel port 26379#227
Merged
Conversation
The egress network policy only allowed port 6379 (Redis master) but blocked port 26379 (Redis Sentinel). The pod connects to Sentinel first to discover the master, so blocking 26379 caused redis.ping() to hang, health probes to timeout, and the pod to be killed by liveness checks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
redis.ping()to hangChanges
networkpolicy.yaml: Add Sentinel port alongside master port in Redis egress rulevalues.yaml: AddredisSentinelPort: 26379config valueTest plan
kubectl logsshowsGET /health 200🤖 Generated with Claude Code