Fix network policy: add GKE service CIDR for Redis#228
Merged
Conversation
The Redis ClusterIP (34.118.226.16) is in GKE's service CIDR, not in 10.0.0.0/8. The network policy was blocking all Redis traffic because the ipBlock rule only covered the pod network. 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
34.118.226.16(GKE service CIDR), NOT in10.0.0.0/8(pod network)ipBlockrule only allowed10.0.0.0/8, blocking all Redis traffic34.118.224.0/20to cover the GKE service CIDRRoot cause
The network policy assumed Redis IPs would be in the pod network (
10.0.0.0/8), but GKE assigns ClusterIPs from a separate service CIDR (34.118.x.x).redis.ping()in the health check was blocked → liveness probe timeout → pod killed.Test plan
🤖 Generated with Claude Code