-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow node-to-node TCP traffic on all ports #54
Merged
Merged
+11
−0
Conversation
This file contains 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
jake-low
force-pushed
the
jlow/allow-internode-tcp
branch
from
January 7, 2025 00:27
931cd5e
to
232572b
Compare
Terraform Format and Style 🖌
|
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.
When I merged #52 today, it caused an outage, so I quickly reverted it (#53). However, the outage wasn't directly caused by my configuration change. What I determined before the rollback was that the ingress-nginx and osmcha-app pods had been deployed to different k8s nodes, and couldn't communicate.
After much debugging today, I found that the default security group settings configured by the Terraform AWS EKS module we use permit inter-node traffic only on unprivileged ports (> 1024). The ingress-nginx pod needs to connect to osmcha-app on port 80, and when the two happened to be deployed on different nodes, the firewall settings were blocking this traffic.
My rollback happened to cause the two pods to once again be scheduled on the same node, restoring service. I suspect we haven't hit this issue in the past because the cluster was in a degraded state (which I noticed and fixed last week) where only one of the two allocated nodes was actually joined to the cluster.
This PR adds a security group rule to allow all traffic between worker nodes (including on privileged ports), which I believe should mean the app can run even when the ingress-nginx and osmcha-app pods are scheduled on different nodes.