- About Pixie
- Installing Pixie
- Using Pixie
Before installing Pixie to your Kubernetes cluster, please ensure that your system meets the requirements below.
Please refer to the install guides for information on how to install Pixie to your K8s cluster.
v1.21+ is required.
The following tables list Kubernetes environments that have been tested with Pixie.
|Supported (includes support on Bottlerocket AMIs)
|Not Supported (Fargate does not support eBPF)
|Not Supported (Autopilot does not support eBPF)
|Generally supported, see requirements below including Linux kernel version.
For local development, we recommend using Minikube with a VM driver (
kvm2 on Linux,
hyperkit on Mac). Note that Kubernetes environments that run inside a container are not currently supported.
|Supported for containerd container runtime (not supported for dockerd runtime)
|Not Supported (k3d runs k3s clusters inside Docker container "nodes")
|Not Supported (kind runs K8s clusters inside Docker container "nodes")
Pixie runs on Linux nodes only. You can configure Pixie to deploy to a subset of the nodes in your cluster.
|Not in roadmap
The following table lists Linux distributions that are known to work with Pixie.
|RedHat Enterprise Linux
Pixie requires an
Pixie requires the following memory per node:
|To accommodate application pods, we recommend using no more than 25% of the nodes' total memory for Pixie.
Pixie deploys its PEMs as a DaemonSet on your cluster in order to collect and store telemetry data. The default memory limit is 2Gi per PEM. The lowest recommended value is 1Gi per PEM. For more information on how to configure Pixie's memory usage, see the Tuning Memory Usage page.
Your cluster's telemetry data flows through Pixie's Cloud via a reverse proxy as encrypted traffic without any persistence. This allows users to access data without being in the same VPC/network as the cluster. Pixie offers end-to-end encryption for telemetry data in flight.