Skip to content
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

docs: explain private networks feature #84

Closed
mxschmitt opened this issue Mar 28, 2020 · 0 comments · Fixed by #85
Closed

docs: explain private networks feature #84

mxschmitt opened this issue Mar 28, 2020 · 0 comments · Fixed by #85

Comments

@mxschmitt
Copy link
Owner

mxschmitt commented Mar 28, 2020

Frequently asked questions

is it secure?

Traffic between Cloud Servers inside a Network is private and isolated, but not automatically encrypted. We recommend you use TLS or similar protocols to encrypt sensitive traffic.

Reference: Hetzner Cloud documentation

The Rancher traffic between the agents and the Rancher related traffic to the nodes is fully encrypted over HTTPS.

The custom application specific traffic is not encrypted. But if you use the Hetzner Private Network, then it's not reachable by other people (Hetzner says that).

Requirements for Private Networks

  • Rancher host needs to be in the same Private Network as the selected one in the Node template.
  • Under the global settings of Rancher the server-url needs to be the internal IP of the Private Network (you can find it in the Hetzner Cloud Console). Otherwise the traffic won't go through the Internal network.

How to close the open ports on the public interface?

https://github.com/vitobotta/hetzner-cloud-init

TODO more verbose description

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant