Stage 17: Data Plane Frontend

Stage 17 deploys the data plane frontend applications: the data plane UI and all workbench applications. Each workbench provides a specialized interface for a different user persona.

Source file: scripts/stages/17-data-plane-frontend.sh

Applications Deployed

Configuration

Ingress Domain Resolution

If INGRESS_DOMAIN is not set, the stage auto-detects the LoadBalancer IP and constructs a nip.io domain:

<lb-ip>.nip.io

In production, each tenant gets a dedicated domain (e.g., acme.matih.ai).

Deployment

Each frontend application is deployed as a separate Helm release:

for app in data-plane-ui bi-workbench ml-workbench data-workbench agentic-workbench; do
    helm upgrade --install ${app} \
        infrastructure/helm/${app} \
        --namespace matih-data-plane \
        --set image.repository=${ACR_URL}/matih/${app} \
        --set image.tag=${IMAGE_TAG} \
        --set ingress.domain=${INGRESS_DOMAIN} \
        --wait --timeout 5m
done

Libraries Used

Dependencies

• Requires: 16-data-plane-services
• Required by: 18-validate

Dependency Verification

kubectl get pods -n matih-data-plane -l app=bi-workbench
kubectl get ingress -n matih-data-plane