GraphScope Interactive Deployment#


git clone
cd GraphScope/charts/
$ helm install {your-release-name} ./graphscope-interactive/

Now you can the endpoint via

$ kubectl describe svc {your-release-name} -graphscope-interactive-frontend | grep "Endpoints:" | awk -F' ' '{print $2}'
# the first is the gremlin endpoint(currently not supported)
# the second is the cypher endpoint

Delete the deployment via

helm delete {your-release-name}

Customizing Configuration#

By default, all pods of GraphScope Interactive is deployed on the same k8s node. In such case, all pods can share the storage via k8s pvc of hostPath kind.

To offer higher throughput and query performance, we also support launching pods across multiple nodes. However, in this mode, you need a storage solution like NFS to ensure that all nodes can access the same storage.

Customize Graph Data.#

By default we provide builtin modern_graph for Interactive. We also support customizing graph data by providing raw graph data via csv files. For detail about Graph Model and DataLoading, please check Interactive Data Model;

Single Node#

If you just want to deploy Interactive on a single node, then you can just put all csv files into a directory, i.e. /tmp/data/.

Then you can create a PV on the node, via the following commands

# 0. Download the template pvc configuration

# 1. Customize the pvc configuration
vim pvc/pvc.yaml
#  path: {} # use the directory where your raw data exists.

# 2. Create the persistent volume on the single node.
kubectl apply -f pvc.yaml

Multiple nodes#

If you want to deploy Interactive on multiple nodes, then you need something like nfs to store you raw graph data, such that all k8s nodes can share the access to same files.


Customize Values.yaml#

  • docker artifacts

    repository: graphscope/interactive
    tag: "v0.2.4"

# docker artifacts for frontend
    repository: graphscope/interactive
    tag: "v0.2.4"
  • pvc

    ## If true, use a Persistent Volume Claim, If false, use emptyDir
    enabled: true
    ## Name of existing PVC to hold GraphScope store data
    ## NOTE: When it's set the rest of persistence parameters are ignored
    existingClaim: "graphscope-interactive-pvc"
    # existingClaim: ""
  • common

  replicaCount: 1 # frontend num
      gremlinPort: 8182 # gremlin service port
  replicaCount: 1 # executor num

# hiactor config
hiactorWorkerNum: 1 # currently only support 1.
hiactorTimeout: 240000