Documentation
  • Introduction
    • How It Works
    • Architecture & Data Flow
    • Why another Agent?
    • eBPF Concepts
    • Use Cases
  • Deployment
  • Qtap
    • Getting Started
    • System Requirements
    • Installation
      • Linux Binary
      • Docker Container
      • Helm Chart
      • Kubernetes Manifest
    • Configuration
      • Storage Configuration
      • Traffic Processing with Plugins
      • Traffic Capture Settings
      • Configuration Examples
  • Qplane
    • Getting Started
      • Create an Account
      • Install Qtap
      • Review your Dashboards
    • Installation
      • Linux Binary
      • Docker Container
      • Helm Chart
    • Configuration
  • Security & Compliance
  • License
  • Appendix
    • Qcontrol (Beta)
    • Java
    • Object Storage
      • Google Cloud Storage
    • S3 Credentials for Qtap using Kubernetes Secrets
  • FAQ
Powered by GitBook
On this page
  • Preflight Check
  • Prerequisites
  • Install Qpoint Helm Repo
  • Deploy Qtap
  • Verifying the Deployment
  • Uninstalling Qtap
  • Important Notes
  1. Qtap
  2. Installation

Helm Chart

PreviousDocker ContainerNextKubernetes Manifest

Last updated 10 days ago

Preflight Check

If you'd like to verify your environment's compatibility, use the :

curl -sSL https://github.com/qpoint-io/preflight/releases/latest/download/preflight.sh | sudo bash

Prerequisites

  • Kubernetes cluster on a Linux Host with supported Kernel (5.10+)

  • Helm

  • Kubectl

Install Qpoint Helm Repo

First, add the Qpoint Helm Repo:

helm repo add qpoint https://helm.qpoint.io/
helm repo update
helm search repo qpoint/qtap --versions
helm show values qpoint/qtap

Deploy Qtap

helm install qtap qpoint/qtap \
  -n qpoint \
  --create-namespace \
  --set logLevel=info \
  --set-file config=./qtap-config.yaml

Verifying the Deployment

To verify that Qtap is running:

kubectl get pods -n qpoint

You should see a pod named qtap-xxxx in the Running state.

Uninstalling Qtap

To uninstall Qtap:

helm uninstall qtap -n qpoint

Important Notes

  1. The Qtap pod requires privileged access for eBPF operations. Ensure your cluster's security policies allow this.

  2. To set a specific version, use --set image.tag="v0.9.7"

  3. For cloud-connected mode, keep your registration token secure and do not share it in public repositories.

  4. For local mode, ensure your configuration is correctly formatted and contains all necessary settings.

  5. The default configuration mounts the host's /sys directory. Ensure this is allowed in your cluster.

  6. You may need to adjust resource requests and limits based on your cluster's capacity and Qtap's requirements.

  7. When using secret management, ensure proper RBAC permissions are in place for accessing the secret.

You'll need to provide your Qtap configuration using a YAML file. First, qtap-config.yaml and supply it via your helm command:

following script
Qtap YAML config file
create your configuration file