• 01 Dec 2021
  • 1 Minute to read


Follow these steps to prepare a kubernetes cluster for the Traceable platform agent installation.


  • Basic understanding of Kubernetes environment along with Kubernetes sidecar.
  • Valid username and password to log into Traceable’s onboarding application.
  • Identify the namespaces which you want to monitor.
  • You can use either the Helm charts or YAML files to install various Traceable components. Identify the one that you would like to use.

Health Checks

Traceable does not support TCP Probes. Given Traceable redirects all incoming traffic to its sidecar, all the TCP ports appear open. The kubelet simply checks for any process listening on the specified port. This makes it appear as if the application is up and running when it may still be initializing. Imagine a four way stoplight with all green lights; this is what's happening in your cluster.

If your organization is using TCP Probes for liveness, you can workaround this issue by switching to httpGet probes.

Traceable proxy injection

Traceable will act as a sidecar to the pods in the namespace you wish to protect. For a pod to be considered for proxy injection, the namespace for the pod should have the label traceableai-inject-proxy=enabled. Enter the following command:

export NAMESPACE=<namespace to protect>

kubectl label namespace $NAMESPACE traceableai-inject-proxy=enabled

You can alternatively add the following to the namespace manifest:

apiVersion: v1
kind: Namespace
    traceableai-inject-proxy: enabled

This enables the default injection of the proxy for all the pods in the namespace.

Next up - Choose an install method


Was this article helpful?

What's Next