Below are the requirements for deploying Pixie to your Kubernetes (K8s) cluster.
Please refer to the install guides for information on how to install Pixie to your K8s cluster.
Kubernetes v1.16+
is required.
K8s Environment | Support |
---|---|
AKS | Supported |
EKS | Supported (includes support on Bottlerocket AMIs) |
EKS Fargate | Not Supported (Fargate does not support eBPF) |
GKE | Supported |
GKE Autopilot | Not Supported (Autopilot does not support eBPF) |
OKE | Supported |
OpenShift | Supported |
kOps | Supported |
Self-hosted | 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.
K8s Environment | Support |
---|---|
Docker Desktop | Not supported |
k0s | Supported |
k3s | Supported |
k3d | Not Supported (k3d runs k3s clusters inside Docker container "nodes") |
kind | Not Supported (kind runs K8s clusters inside Docker container "nodes") |
minikube with driver=kvm2 | Supported |
minikube with driver=hyperkit | Supported |
minikube with driver=docker | Not Supported |
minikube with driver=none | Not Supported |
Pixie requires the following memory per node:
Minimum | Notes |
---|---|
1GiB | 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.
Pixie requires an x86-64
architecture.
Support | |
---|---|
x86-64 | Supported |
ARM | Not supported |
Pixie runs on Linux nodes only.
Support | Version | |
---|---|---|
Linux | Supported | v4.14+ |
Windows | Not Supported | Not in roadmap |
The following is a list of Linux distributions that have been tested.
Version | |
---|---|
Ubuntu | 18.04+ |
Debian | 10+ |
RHEL | 8+ |
CentOS | 7.3+ |
Pixie may also work on other distributions.
Pixie's Vizier Module sends outgoing HTTPS/2 requests to withpixie.ai:443
.
Your cluster's data flows through Pixie's control 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.