Skip to content

Commit

Permalink
chore(k8s): Add a tip about connecting with minikube (#4141)
Browse files Browse the repository at this point in the history
<!--
Thanks for your contribution! please review
https://github.com/alibaba/GraphScope/blob/main/CONTRIBUTING.md before
opening an issue.
-->

## What do these changes do?
As title.

<!-- Please give a short brief about these changes. -->

Add a tip in deployment with helm.

## Related issue number

<!-- Are there any issues opened that will be resolved by merging this
change? -->

Fixes #4124
  • Loading branch information
Thespica authored Aug 16, 2024
1 parent 62bd13e commit 049fe92
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions docs/deployment/deploy_graphscope_with_helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,17 @@ You'll need `graphscope-client` package to `import graphscope`.
Since the GraphScope has been running in the cluster, you only need to **connect** to it.
Other than the connection procedure, other statements are identical to those GraphScope clusters launched by Python client.

````{tip}
If you meet connection problems with minikube, try getting the service name and exposing the service like this:
```bash
# kubectl get services
minikube service coordinator-service-<release-name> --url
```
For more usage, you could refer to [minikube's accessing tutorial](https://minikube.sigs.k8s.io/docs/handbook/accessing/).
````

```python
import graphscope
graphscope.set_option(show_log=True)
Expand Down

0 comments on commit 049fe92

Please sign in to comment.