Configuration

Qtap offers two flexible management approaches, catering to different deployment needs and preferences: through a local YAML configuration or via the cloud control plane. Both methods are supported for all installations.

Local Configuration

This method utilizes a local qtap-config.yaml file to configure the Qtap settings directly on the container. This approach is beneficial for scenarios requiring precise, file-based configuration control, particularly when deploying in environments where direct file manipulation is feasible.

Helm Example:

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

Cloud Connected Configuration

Alternatively, Qtap can be managed remotely via the Qpoint cloud control plane. This option is ideal for users who prefer centralized management through a control plane API, offering ease of configuration and scalability across multiple Qtap instances without the need to directly access each deployment.

Docker Example:

helm install qpoint-tap qpoint/qpoint-tap \
  -n qpoint \
  --create-namespace \
  --set logLevel=info \
  --set registrationToken=$TOKEN