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
In kubernetes it is normal to expose external services via LoadBalancer with External IP (for example metallb).
With gravity, when you want to create a cluster of, for example, 3 nodes in different kubernetes clusters, it has not been possible, at least for me.
Since if I do not define the INSTANCE_IP variable, it takes the IP of the pod. If I define the INSTANCE_IP variable with the external IP of the LoadBalancer service, the pod does not start, since it does not have that IP locally.
Would it be possible to define a variable such as EXTERNAL_IP or something similar to be able to identify with gravity instances that are not in the same kubernetes cluster? Thanks!
In kubernetes it is normal to expose external services via LoadBalancer with External IP (for example metallb).
With gravity, when you want to create a cluster of, for example, 3 nodes in different kubernetes clusters, it has not been possible, at least for me.
Since if I do not define the INSTANCE_IP variable, it takes the IP of the pod. If I define the INSTANCE_IP variable with the external IP of the LoadBalancer service, the pod does not start, since it does not have that IP locally.
Would it be possible to define a variable such as EXTERNAL_IP or something similar to be able to identify with gravity instances that are not in the same kubernetes cluster? Thanks!
gravity1:
gravity2:
gravity3:
error example gravity1:
The text was updated successfully, but these errors were encountered: