[WIP] Adapt to the vineyard deployed with kubernetes DaemonSet object #145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Make GraphScope run on top of DaemonSet vineyard.
Please give a short brief about these changes.
Add a session parameter
vineyard_socket
, which is a path of vineyard socket file.In K8s cluster, it will mount this path as a hostPath volume with Socket type. Or GraphScope will launch a vineyard container inside engine pods and a random socket will be created if param missing.
Notes
This pr cannot be merged yet caused by the following reasons:
interactive.subgraph
need a vineyard rpc endpoint.namespace
andname
Related issue number
Fixes #89