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

no public IP for API loadbalancer #369

Open
jampy opened this issue May 29, 2024 · 0 comments
Open

no public IP for API loadbalancer #369

jampy opened this issue May 29, 2024 · 0 comments

Comments

@jampy
Copy link

jampy commented May 29, 2024

I would like to restrict k8s API access to a Hetzner private network.

Using existing_network I can configure hetzner-k3s to attach all nodes to a pre-existing private network, fine.

Questions:

  • is there an option to have hetzner-k3s automatically attach the API load balancer (created by hetzner-k3s) to the same network?
  • is there an option to disable the public interface on the API load balancer, so that it is reachable via the private network only

or, alternatively:

  • can I pre-configure a Hetzner load balancer (just as described above) and have hetzner-k3s reuse it, similarily to existing_network?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant