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
Hello! I'm really new on this topic, and I'm trying to translate what I learned from the "Local playground for testing and development" example to my own 3 cluster setup (one of them with the edgeDNS resolver), these clusters are connected on my company's network. So far, this is the DNSEndpoint on an app I deployed in my 2 different clusters
The "localtargets-liqo.cloud.testanim.uzmar" targets correctly show the node IPs for each cluster. However, as I understand, the "liqo.cloud.testanim.uzmar" targets should show all the IPs of both of my cluster's nodes. Any idea what could be going wrong?
Also, my Edge DNS resolver running on ip 10.171.61.137 and with the 30053 port open, shows the following
Hi @uzmargomez Thanks a lot for trying out the project, I am happy that it worked! I was not fast enough here but please don't hesitate to ask if you have any more questions :)
Hello! I'm really new on this topic, and I'm trying to translate what I learned from the "Local playground for testing and development" example to my own 3 cluster setup (one of them with the edgeDNS resolver), these clusters are connected on my company's network. So far, this is the DNSEndpoint on an app I deployed in my 2 different clusters
Cluster 1
Cluster 2
The "localtargets-liqo.cloud.testanim.uzmar" targets correctly show the node IPs for each cluster. However, as I understand, the "liqo.cloud.testanim.uzmar" targets should show all the IPs of both of my cluster's nodes. Any idea what could be going wrong?
Also, my Edge DNS resolver running on ip 10.171.61.137 and with the 30053 port open, shows the following
and
but when trying to access liqo.cloud.testanim.uzmar directly, I get the following
I wonder if there is something I may be misunderstanding. Thanks for any help or advise that you can provide!
The text was updated successfully, but these errors were encountered: