You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The nodes in this cluster use their public IP addresses for intra-cluster communication.
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.
The text was updated successfully, but these errors were encountered: