Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Istio Service Mesh #116

Open
FerMiguelao opened this issue Feb 18, 2025 · 2 comments
Open

Support for Istio Service Mesh #116

FerMiguelao opened this issue Feb 18, 2025 · 2 comments

Comments

@FerMiguelao
Copy link

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!

@antejavor
Copy link
Collaborator

Hi @FerMiguelao, thanks for reporting this. Could you let me know if you've been able to deploy Memgraph and bypass this problem?

We will probably improve this, but we do not have a timeline. BTW. What are you building?

@FerMiguelao
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants