Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt

Use this file to discover all available pages before exploring further.

To get started with Chronosphere Telemetry Pipeline on Kubernetes, you’ll need to install a Core Operator in each Kubernetes cluster where you want to deploy pipelines.

​
Supported Kubernetes distributions

Telemetry Pipeline is compatible with the following distributions of Kubernetes:
  • Open Source Kubernetes 1.25 or later
  • Amazon Kubernetes Service (EKS)
  • Azure Kubernetes Service (AKS)
  • Google Kubernetes Engine (GKE)
  • Red Hat Open Shift 4.0 or later

​
Installation steps

You can use Pipeline CLI or Helm to install a Core Operator in a Kubernetes cluster.
When you install a Core Operator, only deploy a single replica. If a Core Operator has multiple replicas, those replicas will conflict with one another.
  1. Review the Telemetry Pipeline installation prerequisites.
  2. Install or update Pipeline CLI. Because Core Operator versions are dependent on your Pipeline CLI version, keeping Pipeline CLI current ensures that you’re installing the latest version of Core Operator.
  3. If you haven’t already, set an API token in Pipeline CLI.
  4. Ensure that the KUBECONFIG environment variable in your cluster is set to a valid configuration file.
  5. Run the following command to install a Core Operator: 
    calyptia install operator
    Optionally, you can add the --kube-namespace command to set that Core Operator’s namespace.
  6. Repeat these steps for each Kubernetes cluster where you want to use Telemetry Pipeline.

​
View installation logs

After you install a Core Operator in a Kubernetes cluster, use the following kubectl command to view logs from the installation process: 
kubectl logs deploy/calyptia-core-controller-manager

​
Next steps

After you’ve installed a Core Operator in your Linux environment, you can create a Core Instance in that environment.