Advanced Installation: Helm

The advanced installation includes the Liveness and Identification features. The setup is based on the integration with PostgreSQL DB and Milvus vector database.

Before starting the installation, note that as Milvus is quite demanding, you need to plan the infrastructure in advance. Before you install Milvus, check whether your hardware and software meet the Kubernetes prerequisites.

For further performance and integration fine-tuning, refer to the official Milvus documentation.

Liveness Assessment

To install the chart with the release name my-release and Liveness capabilities:

helm install my-release regulaforensics/faceapi \
    --set licenseSecretName=faceapi-license \
    --set config.service.liveness.enabled=true \
    --set postgresql.enabled=true

Face Identification (Search)

To install the chart with the release name my-release and Search capabilities:

helm install my-release regulaforensics/faceapi \
    --set licenseSecretName=faceapi-license \
    --set config.service.search.enabled=true \
    --set milvus.enabled=true \
    --set postgresql.enabled=true

Liveness and Search

To install the chart with the release name my-release and Search capabilities:

helm install my-release regulaforensics/faceapi \
    --set licenseSecretName=faceapi-license \
    --set config.service.liveness.enabled=true \
    --set config.service.search.enabled=true \
    --set milvus.enabled=true \
    --set postgresql.enabled=true

GPU Version

The GPU version shows dramatically higher performance than the CPU version.

Prerequisites

• GPU Nodes. The GPU version requires nvidia gpu nodes, refer to https://github.com/NVIDIA/k8s-device-plugin.
• The gpu version tag is set, for example, latest-gpu
• Propper resources section.

latest-gpu

resources:
  requests:
    nvidia.com/gpu: 1
  limits:
    nvidia.com/gpu: 1

External Dependencies

FaceAPI can be configured to use external dependencies.

• External object storage
• External etcd
• External Pulsar
• External PostgreSQL

External PostgreSQL

External PostgreSQL can be configured via the following values:

1. externalPostgreSQL, for example, postgresql://user:pass@host:5432/database.

2. externalPostgreSQLSecret, for example, postgresql://user:pass@host:5432/database. (Taking a value from the secret is a secure way.)

For details, see the Configuration page.