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
While implementing standalone memgraph inside a k8s cluster, found out that some ports are not following the correct naming convention. Istio Config MessageIstio naming convention
Running istioctl analyze -n memgraph-database returns the following: Info [IST0118] (Service memgraph-database/memgraph-database) Port name bolt-port (port: 7687, targetPort: 7687) doesn't follow the naming convention of Istio port.
This should be fixable either by renaming the port names to tcp- or by making the port names variables
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi @antejavor! Hope you are doing well! Yes, I was able to deploy Memgraph using service type Loadbalancer as a workaround for now. It's not optimal as our whole infra is using service mesh, but will do for now.
We are building some pocs for our project, so there is still not much defined yet.
While implementing standalone memgraph inside a k8s cluster, found out that some ports are not following the correct naming convention. Istio Config Message Istio naming convention
Running
istioctl analyze -n memgraph-database
returns the following:Info [IST0118] (Service memgraph-database/memgraph-database) Port name bolt-port (port: 7687, targetPort: 7687) doesn't follow the naming convention of Istio port.
This should be fixable either by renaming the port names to tcp- or by making the port names variables
Thanks in advance!
The text was updated successfully, but these errors were encountered: