Skip to main content
Version: 0.9.x

Installation

Download and install issues​

  • check your API Key
  • check you don't have any connectivity issues (VPN, firewalls, etc)
  • use Helm version 2.13 or above.
    If not, please upgrade using your preferred method from the documentation.
helm version
version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}
  • Do you have docker running?
    docker version should include a Server: section with info regarding your local docker server.
docker version

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:34 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:29:19 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
# Not working example:
docker version

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:34 2019
 OS/Arch:           darwin/amd64
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
  • Do you have privilege to save to your local docker registry?
    You can check that by pulling a local image to it:
docker pull alpine:latest

latest: Pulling from library/alpine
aad63a933944: Pull complete
Digest: sha256:b276d875eeed9c7d3f1cfa7edb06b22ed22b14219a7d67c52c56612330348239
Status: Downloaded newer image for alpine:latest
docker.io/library/alpine:latest
  • Is TSB installed?
    TSB (New version of TCC) have to be installed first. Ensure everything is installed and running in Kubernetes. Using the kubectl command, list the pods in the tcc Namespace and ensure they are all in a Running or Completed status. There may be some delays to get there when you first install TSB. Please allow up to 5 minutes for pods to start.
kubectl -n tcc get pods

NAME                              READY   STATUS      RESTARTS   AGE
envoy-8664477cf9-5wps2            1/1     Running     0          43h
iam-65ccb65464-qqzfx              1/1     Running     0          43h
oap-deployment-68fcb5f5fc-qtkrr   1/1     Running     0          43h
otel-collector-668dbc5bdd-drq8p   1/1     Running     0          43h
spm-6cc454df68-bzhvz              1/1     Running     0          43h
tcc-667b47f8db-7vrm9              1/1     Running     0          43h
teamsync-1585126800-4bqbx         0/1     Completed   0          133m
teamsync-1585130400-z5v2n         0/1     Completed   0          73m
teamsync-1585134000-x4782         0/1     Completed   0          13m
web-74ff449b4-8c4zx               1/1     Running     0          43h
zipkin-5dd86cf46-wwpqf            1/1     Running     0          43h
note

This is a sample list and you may not see all the pods you see here, or you may have some others like Elasticsearch or Postgres.

  • Is Control Plane (Istio) installed?
    Each cluster should have an Istio Control Plane deployed. You can ensure everything is working by checking the pods status in the istio-system Namespace. All pods should be in the Running status and the Ready numbers should all be 1/1 or 2/2.
kubectl -n istio-system get pods

NAME                              READY   STATUS    RESTARTS   AGE
istio-tracing-6865844c67-rrfp7    2/2     Running   0          43h
istiod-5b5cd78b7b-987df           1/1     Running   0          43h
oap-deployment-6b986bcbcc-6xwnp   2/2     Running   0          43h
otel-collector-88f6c5f7f-phx5t    2/2     Running   0          43h
tsbd-fbffc856b-6f46l              1/1     Running   0          43h
vmgateway-754b7b68dd-x2zxg        1/1     Running   0          43h

  • Firewall ports and connectivity from Control Plane (Istio) to TSB/TCC is OK?
    The Control Plane in your cluster should be able to reach the TSB (or TCC) namespace's services to register themselves. Ensure your network and Firewall setup allows this.

  • a Gateway inside a user's Application can reach the Control Plane (Istio)?
    An application's Gateway should be able to reach some ports from services in the istio-system Namespace. If your Gateway does not get its configuration, check your firewall rules and network connectivity between nodes.

  • OAP is not in the Running state
    The OAP component needs to connect to Elasticsearch to be able to run. As this component is not provided by the TSB installation, you have to ensure it is installed, running and is reachable by OAP.