apache/skywalking-helm repository overview

⁠Apache SkyWalking Helm Chart

Deploy Apache SkyWalking⁠ on Kubernetes: the OAP backend, the Horizon UI web console, an optional Satellite gateway, and a storage backend the chart can deploy for you.

Requires Helm 3.8 or newer — earlier versions cannot pull oci:// charts.

⁠Install

The chart's default storage is Elasticsearch, deployed through ECK⁠. ECK's CRDs must exist before the chart renders, so install them first:

helm install eck-crds eck-operator-crds \
  --repo https://helm.elastic.co --version 3.3.1 \
  -n skywalking --create-namespace

helm install skywalking oci://registry-1.docker.io/apache/skywalking-helm \
  --version 5.0.0 -n skywalking --create-namespace \
  --set oap.image.tag=11.0.0 \
  --set oap.storageType=elasticsearch \
  --set ui.image.tag=horizon-1.0.0 \
  --set eck-operator.installCRDs=false

Prefer BanyanDB, SkyWalking's own storage engine? No CRDs needed, and it is much lighter than a three-node Elasticsearch:

helm install skywalking oci://registry-1.docker.io/apache/skywalking-helm \
  --version 5.0.0 -n skywalking --create-namespace \
  --set oap.image.tag=11.0.0 \
  --set oap.storageType=banyandb \
  --set ui.image.tag=horizon-1.0.0 \
  --set elasticsearch.enabled=false \
  --set banyandb.enabled=true \
  --set banyandb.image.tag=0.11.0

elasticsearch.enabled defaults to true, so switching storage means turning it off explicitly — otherwise the chart also installs an Elasticsearch cluster nothing uses.

⁠Required values

Three values have no default and must be set on every install. The chart fails fast, at render time, if any is missing.

banyandb.image.tag is required as well whenever banyandb.enabled=true.

Set them with --set, or collect them in a file and pass -f my-values.yaml. Every value the chart accepts is listed in the Chart Values reference⁠.

⁠A fresh install has no login

Horizon UI ships no default credentials, and it does not fail closed: the pod reports Ready, the login page renders, and no username or password is accepted until you configure users. Set HORIZON_AUTH_LOCAL_USERS to a JSON array of users — from a Kubernetes Secret in production:

ui:
  envFromSecret: skywalking-ui-users

Set Up Logins⁠ covers generating the Argon2id password hashes, a throwaway demo login, and the Secret-based setup.

⁠Version compatibility

OAP 11 pins the BanyanDB server API version it accepts and refuses to start against a mismatch, so these three move together:

The legacy booster UI is not supported from chart 5.0.0: SkyWalking 11.0.0 removed it from the distribution, so apache/skywalking-ui publishes no 11.x tag — only horizon-* tags. See Version Compatibility⁠ and the Upgrade guide⁠.

⁠Documentation

• Full documentation⁠
• Quick Start⁠
• Pick a Storage Backend⁠
• Troubleshooting⁠
• Changelog⁠
• SkyWalking backend setup⁠

⁠Source

github.com/apache/skywalking-helm⁠

⁠Contact us

• Submit an issue⁠
• Mailing list: [email protected]⁠. Mail to [email protected], then follow the reply to subscribe.
• Send a Request to join SkyWalking slack mail to the mailing list and we will invite you. Chinese speakers, use [CN] Request to join SkyWalking slack.
• Twitter: ASFSkyWalking⁠
• bilibili B站 视频⁠

⁠License

Apache 2.0⁠