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.

Docker Command:

docker run \
  --user 0:0 \
  --privileged \
  --cap-add CAP_BPF \
  --cap-add CAP_SYS_ADMIN \
  --pid=host \
  --network=host \
  -v /sys:/sys \
  -v "$(pwd):/app/config" \
  -e TINI_SUBREAPER=1 \
  --ulimit=memlock=-1 \
  us-docker.pkg.dev/qpoint-edge/public/qpoint:v0.1.6 \
  tap \
  --log-level=info \
  --log-encoding=console \
  --qpoint-config=/app/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 Command:

docker run \
  --user 0:0 \
  --privileged \
  --cap-add CAP_BPF \
  --cap-add CAP_SYS_ADMIN \
  --pid=host \
  --network=host \
  -v /sys:/sys \
  -e TINI_SUBREAPER=1 \
  --ulimit=memlock=-1 \
  us-docker.pkg.dev/qpoint-edge/public/qpoint:v0.1.6 \
  tap \
  --log-level=info \
  --log-encoding=console \
  --registration-token=$TOKEN

Both approaches provide the flexibility to configure Qtap according to your specific needs. The local configuration method allows for detailed, hands-on management, while the cloud-connected approach offers centralized control and easier management of multiple instances.

Last updated