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
We have setup of three nodes of community edition on Kubernetes cluster. While using asamd/aql eithin the cluster nodes, it works as the Nodes are binding with POD IP. However, the external access doesn't work, since the POD IP is inaccessible from outside network.
What are the provision to enable the binding of IP address, like LB IP with Nodes?
We have tried configure as follows, where alternate-access-address consists of LB IP :
network {
service {
address any
#access-address 192.168.144.152 192.168.144.153
alternate-access-address 192.168.144.152 192.168.144.153
port 3000
}
Please specify the right config for accessing the three or more node cluster from external clients
The text was updated successfully, but these errors were encountered:
We have setup of three nodes of community edition on Kubernetes cluster. While using asamd/aql eithin the cluster nodes, it works as the Nodes are binding with POD IP. However, the external access doesn't work, since the POD IP is inaccessible from outside network.
What are the provision to enable the binding of IP address, like LB IP with Nodes?
We have tried configure as follows, where alternate-access-address consists of LB IP :
Please specify the right config for accessing the three or more node cluster from external clients
The text was updated successfully, but these errors were encountered: