Kubernetes Deployment

This guide walks you through using the Tracetest CLI to deploy Tracetest with Kubernetes.

note

This is an example of a production-ready deployment, but real-world deployments can vary significantly depending on desired performance and scale.

This setup is ideal for CI/CD environments and QA teams working in shared environments. You can use a remote or local (minikube, kind, etc) cluster.

We'll even help you setup a local cluster, if you need one.

After installing the CLI, run:

tracetest server install

Expected output

How do you want to run TraceTest? [type to search]:
  Using Docker Compose
> Using Kubernetes

Select Using Kubernetes and follow the instructions.

Tools required (installed if missing):

• kubectl
• Helm

If you selected to run locally and want the installer to set up minikube for you:

• Docker

Requirements:

• Jaeger or other compatible backend. If missing, the installer will help you configure one.
• OpenTelemetry Collector. If missing, the installer will help you configure one.

Optionals:

• PokeShop demo app. A sample microservice app to test your Tracetest installation.

Result:

• tracetest Helm chart deployed in the tracetest (configurable) namespace.
• Jaeger instance deployed in the tracetest namespace, if selected.
• Cert Manager, if selected.
• Jaeger Operator, if selected.
• OpenTelemetry Collector deployed in the tracetest (configurable) namespace, if selected.
• PokeShop demo app deployed in the demo namespace, if selected.

How to start:

Once installed, you can get started by launching Tracetest:

kubectl port-forward svc/tracetest 11633

Then launch a browser to http://localhost:11633/.

For more configuration options, read more in the configuration docs.