Verifying the installation
After running the Helm upgrade command, follow these steps to verify that the DataQI platform has successfully deployed and is running correctly in your cluster.
1. Check pod health
Section titled “1. Check pod health”kubectl get pods -n <namespace>All pods should reach the Running status. Here are the key services to confirm:
| Component | Expected pods |
|---|---|
| API | 2/2 Running (app + token-broker sidecar) |
| Telemetry ingress | 1/1 Running |
| Extractor | 2/2 Running |
| SPA | 1/1 Running |
| Keycloak | 1/1 Running |
| NATS | 1/1 Running |
| Valkey | 1/1 Running |
2. Check ingress / routing
Section titled “2. Check ingress / routing”Ensure your cluster has successfully assigned an address or load balancer to the routing resources.
AKS / Gateway API (HTTPRoute):
kubectl get httproute -n <namespace>OpenShift (Ingress):
kubectl get ingress -n <namespace>The four core routes (api, telemetry-ingress, keycloak, spa) should show an ADDRESS. The telemetry route uses the API hostname with the more specific /telemetry path.
3. Verify DNS resolution
Section titled “3. Verify DNS resolution”Verify that the DNS records you configured are correctly resolving to the ingress address from your local machine:
nslookup dataqi.<your-domain>nslookup api-dataqi.<your-domain>nslookup auth-dataqi.<your-domain>4. Check the SPA configuration
Section titled “4. Check the SPA configuration”The single-page application requires a configuration map injected at runtime. Verify that this was generated correctly:
kubectl get configmap spa-config -n <namespace> -o jsonpath='{.data.config\.json}'Confirm that the baseUrl, apiBaseUrl, and authority properties all reflect your correct external domain. When both telemetry ingress and the collector are enabled, telemetry.enabled should be true.
5. Smoke test
Section titled “5. Smoke test”Open https://dataqi.<your-domain> in your browser. If everything is configured correctly, you should be redirected to the DataQI login page.
Open https://dataqi.<your-domain>/docs/ in the same browser. The documentation home page and search must load without requiring sign-in. You can inspect its packaged version metadata at:
https://dataqi.<your-domain>/docs/version.jsonThe canonicalVersion, commitSha and buildTimeUtc values must match the SPA metadata returned by /version.json.