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

Use Private IPs and backend transfer for internal node addresses #80

Open
displague opened this issue Mar 22, 2024 · 0 comments
Open

Use Private IPs and backend transfer for internal node addresses #80

displague opened this issue Mar 22, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@displague
Copy link
Member

displague commented Mar 22, 2024

The nodes in this cluster use their public IP addresses for intra-cluster communication.

root@k3s-demo-cluster-k3s-cp-aio:~# kubectl get nodes -o wide
NAME                          STATUS   ROLES                  AGE     VERSION        INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION    CONTAINER-RUNTIME
k3s-demo-cluster-k3s-cp-aio   Ready    control-plane,master   5m41s   v1.28.7+k3s1   145.xx.xx.xx   <none>        Debian GNU/Linux 11 (bullseye)   5.10.0-28-amd64   containerd://1.7.11-k3s2

For demo purposes, with more consideration of best practices and security concerns, these POC nodes should be deployed with public and private addresses. Project Backend Transfer should be used to ensure the cluster nodes can communicate across metros.

The public addresses could then be used for exposing services on public node ips.

@displague displague added the enhancement New feature or request label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant