Skip to content

Memgraph values updated#1050

Open
EvanDietzMorris wants to merge 23 commits intomemgraphfrom
memgraph-values-updated
Open

Memgraph values updated#1050
EvanDietzMorris wants to merge 23 commits intomemgraphfrom
memgraph-values-updated

Conversation

@EvanDietzMorris
Copy link
Collaborator

  • updates all of the values files for the new neo4j & memgraph format
  • go ahead and force the app.neo4j.dataUrl format and remove dataUrl from the top level, we'll fix things if they break
  • add new schema and graph-metadata files to plater but keep them optional

@EvanDietzMorris EvanDietzMorris requested a review from hyi February 8, 2026 08:30
Copy link
Contributor

@hyi hyi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Since the PR is to be merged into the memgraph branch, I am approving it so you can merge it. Then we will need to test memgraph deployment once you return to work to make sure everything indeed works before merging the memgraph branch to master.

@hyi
Copy link
Contributor

hyi commented Feb 8, 2026

@EvanDietzMorris Just a quick note that resources needed for memgraph will need to be configured for each plater instance in values-populated.yaml file, similar to the neo4j block before deploying memgraph backend plater instances. I've got translator kg plater instances for both memgraph and neo4j backends deployed successfully in translator-dev namespace, so I think adding a memgraph block in values-populated.yaml file for each plater instance should be sufficient to deploy a memgraph plater instance.

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

Successfully merging this pull request may close these issues.

2 participants

Comments