This is my first time configuring the various components of Livekit on a Kubernetes cluster in GCP (GKE)
Attached are screenshots of my PODs logs
Server:
Ingress:
Egress:
I have several doubts, I will order them by relevance:
What is the reason for the infinite loop in ingress?
The recommended configuration uses use_external_ip in RTC for both server and ingress. In both cases the logs show failed to get external ip {“nodeID”: “NE_5vZqJMs5a8T8”, “local”: “10.48.2.28”, “err”: “could not validate external IP: 34.31.70.111”}, what is the reason?
Here are the details of my GKE configuration: regional cluster with a single zone, public nodes, n2d-highcpu-8 machines. Currently I have only one node on which I host server, ingress and egress because I am in the configuration phase (later I will increase the number of nodes and configure autoscaling).
I also attach the .yaml that I am applying (I generated them from the Helm Charts)
This is my first time configuring the various components of Livekit on a Kubernetes cluster in GCP (GKE)
Attached are screenshots of my PODs logs
Server:
Ingress:
Egress:
I have several doubts, I will order them by relevance:
use_external_ipin RTC for both server and ingress. In both cases the logs showfailed to get external ip {“nodeID”: “NE_5vZqJMs5a8T8”, “local”: “10.48.2.28”, “err”: “could not validate external IP: 34.31.70.111”}, what is the reason?Here are the details of my GKE configuration: regional cluster with a single zone, public nodes,
n2d-highcpu-8machines. Currently I have only one node on which I host server, ingress and egress because I am in the configuration phase (later I will increase the number of nodes and configure autoscaling).I also attach the .yaml that I am applying (I generated them from the Helm Charts)
livekit-egress-test.txt livekit-ingress-test.txt livekit-server-test.txt