-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
[Bug]: Outgoing TCP connections fail on newly created cluster #1459
Labels
bug
Something isn't working
Comments
You have outbound firwall rules activated: terraform-hcloud-kube-hetzner/kube.tf.example Lines 650 to 651 in da24fd2
These rules are applied by default: terraform-hcloud-kube-hetzner/locals.tf Lines 297 to 344 in da24fd2
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hey all,
Outgoing TCP connections seem to fail on a newly created cluster due to
TCP error 35 / Connection reset by peer
. I noticed this at first as one service connecting to MS SQL failed, which I tried to diagnose for SQL-specific issues, until I noticed that it seems to be the case for multiple or all outgoing requests, regardless of SQL.The exact same container images, YAML files, and configuration are used on another cluster (Azure AKS-based) where all of these requests work perfectly. Thus, this is ensured to be specific to the cluster.
Example call to MS SQL
Example call to Azure Service Bus
Kube.tf file
Screenshots
No response
Platform
Linux
The text was updated successfully, but these errors were encountered: