| tag | f6260e5e051b7fd45cc500b85f108832e75beaa2 | |
|---|---|---|
| tagger | kezhenxu94 <kezhenxu94@163.com> | Sat Oct 31 15:50:42 2020 +0800 |
| object | d4d4cd1a1210d620d886f687211f43bf45d18d93 |
Release 4.0.0
| commit | d4d4cd1a1210d620d886f687211f43bf45d18d93 | [log] [tgz] |
|---|---|---|
| author | kezhenxu94 <kezhenxu94@apache.org> | Sat Oct 31 15:18:05 2020 +0800 |
| committer | GitHub <noreply@github.com> | Sat Oct 31 15:18:05 2020 +0800 |
| tree | 74e317110d52677b3cb6c80ad22f9b1dbac45a74 | |
| parent | fd2eb3090e2ee68662ec5fd065de8a2c8ce4e663 [diff] |
Change logs for 4.0.0 (#62) * Change logs for 4.0.0 * Skip tests when only .md files are modified
SkyWalking Kubernetes repository provides ways to install and configure SkyWalking in a Kubernetes cluster. The scripts are written in Helm 3.
Chart detailed configuration can be found at Chart Readme
There are required values that you must set explicitly when deploying SkyWalking.
| name | description | example |
|---|---|---|
oap.image.tag | the OAP docker image tag | 8.1.0-es6, 8.1.0-es7, etc. |
oap.storageType | the storage type of the OAP | elasticsearch, elasticsearch7, etc. |
ui.image.tag | the UI docker image tag | 8.0.1, 8.1.0, ect. |
You can set these required values via command line (e.g. --set oap.image.tag=8.1.0-es6 --set oap.storageType=elasticsearch), or edit them in a separate file(e.g. values-es6.yaml, values-es7.yaml) and use -f <filename> or --values=<filename>.
git clone https://github.com/apache/skywalking-kubernetes cd skywalking-kubernetes/chart helm repo add elastic https://helm.elastic.co helm dep up skywalking export SKYWALKING_RELEASE_NAME=skywalking # change the release name according to your scenario export SKYWALKING_RELEASE_NAMESPACE=default # change the namespace according to your scenario
In theory, you can deploy all versions of SkyWalking that are >= 6.0.0-GA, by specifying the desired oap.image.tag/ui.image.tag.
Please note that some configurations that are added in the later versions of SkyWalking may not work in earlier versions, and thus if you specify those configurations, they may take no effect.
here are some examples.
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}" \ --set oap.image.tag=8.0.1-es6 \ --set oap.storageType=elasticsearch \ --set ui.image.tag=8.0.1 \ --set elasticsearch.imageTag=6.8.6
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}" \ --set oap.image.tag=8.1.0-es7 \ --set oap.storageType=elasticsearch7 \ --set ui.image.tag=8.1.0 \ --set elasticsearch.imageTag=7.5.1
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}" \ --set oap.image.tag=6.6.0-es7 \ --set oap.storageType=elasticsearch7 \ --set ui.image.tag=6.6.0
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}" \ --set oap.image.tag=6.5.0 \ --set oap.storageType=elasticsearch \ --set ui.image.tag=6.5.0
NOTE: Please make sure the specified OAP image tag supports the specified Elasticsearch version.
Modify the connection information to the existing elasticsearch cluster in file values-my-es.yaml.
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}" \ -f ./skywalking/values-my-es.yaml
Put your own configuration files according to the overridable files under the working directory, files/conf.d, they will override the counterparts in the Docker image.
The SkyWalking OAP exposes many configurations that can be specified by environment variables, as listed in the main repo. You can set those environment variables by --set oap.env.<ENV_NAME>=<ENV_VALUE>, such as --set oap.env.SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=k8s-mesh.
The environment variables take priority over the overrode configuration files.
dev-subscribe@skywalking.apache.org, follow the reply to subscribe the mail list.skywalking channel at Apache Slack. If the link is not working, find the latest one at Apache INFRA WIKI.Apache 2.0