You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wu...@apache.org on 2019/12/12 06:37:09 UTC

[skywalking-kubernetes] branch master updated: Delete how-to-deploy.md

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-kubernetes.git


The following commit(s) were added to refs/heads/master by this push:
     new a840960  Delete how-to-deploy.md
a840960 is described below

commit a840960b0d0abf5a1b33f68b4be40a9ce76b233e
Author: 吴晟 Wu Sheng <wu...@foxmail.com>
AuthorDate: Thu Dec 12 14:37:04 2019 +0800

    Delete how-to-deploy.md
---
 docs/how-to-deploy.md | 36 ------------------------------------
 1 file changed, 36 deletions(-)

diff --git a/docs/how-to-deploy.md b/docs/how-to-deploy.md
deleted file mode 100644
index 81b372a..0000000
--- a/docs/how-to-deploy.md
+++ /dev/null
@@ -1,36 +0,0 @@
-### How to use the SkyWalking Chart?
-
-Two ways:
-- deploy SkyWalking and Elasticsearch (default)
-- only deploy SkyWalking ,and use existing Elasticsearch
-
-#### Deploy SkyWalking and Elasticsearch (default)
-
-```shell script
-$ cd chart
-
-$ helm add stable https://kubernetes-charts.storage.googleapis.com/
-
-$ helm dep up 
-
-$ helm install <release_name> skywalking -n <namespace>
-```
-
-#### Only deploy SkyWalking ,and use existing Elasticsearch
-
-If not want to deploy a new elasticsearch cluster, this way can be solved.
-
-Only need to close the elasticsearch deployed by chart default and configure the existing elasticsearch connection method.
-
-```shell script
-$ cd chart
-
-$ helm add stable https://kubernetes-charts.storage.googleapis.com/
-
-$ helm dep up 
-
-$ helm install <release_name> skywalking -n <namespace> \
-        --set elasticsearch.enabled=false \
-        --set elasticsearch.config.host=<es_host> \
-        --set elasticsearch.config.port.http=<es_port>
-```
\ No newline at end of file