From 049fe925e0369a23d7e1ebfdd5bc2eb3ab52b9cf Mon Sep 17 00:00:00 2001
From: John <thespica@qq.com>
Date: Fri, 16 Aug 2024 17:11:56 +0800
Subject: [PATCH] chore(k8s): Add a tip about connecting with minikube (#4141)

<!--
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
---
 docs/deployment/deploy_graphscope_with_helm.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/deployment/deploy_graphscope_with_helm.md b/docs/deployment/deploy_graphscope_with_helm.md
index fa0015ac9084..348bf82215a8 100644
--- a/docs/deployment/deploy_graphscope_with_helm.md
+++ b/docs/deployment/deploy_graphscope_with_helm.md
@@ -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)