Skip to main content

Post-Installation Validation

After the installer completes, validate that all Access Analyzer components are running correctly.

Cluster Health

Verify that all Kubernetes pods are healthy:

kubectl get pods -A -o wide

All pods should be in one of these states:

StatusMeaning
RunningPod is active and healthy
CompletedOne-time job completed successfully

If any pods show CrashLoopBackOff, Error, or ImagePullBackOff, check the application logs.

ArgoCD Application Status

Check the sync and health status of all ArgoCD-managed applications:

kubectl get apps -n argocd

Each application should show:

FieldExpected Value
SYNC STATUSSynced
HEALTH STATUSHealthy

ArgoCD UI

Access the ArgoCD web interface for a visual overview of all applications:

  1. Start port forwarding:

    kubectl port-forward svc/argocd-server -n argocd 8090:443
  2. Open https://localhost:8090 in a browser

  3. Retrieve the admin password:

    kubectl -n argocd get secret argocd-initial-admin-secret \
    -o jsonpath='{.data.password}' | base64 -d; echo
  4. Sign in with username admin and the retrieved password

The ArgoCD dashboard displays each application's sync status, health, and resource tree.

Application Health Table

The following components should be deployed and healthy after a successful installation:

ComponentNamespaceType
Core APIaccess-analyzerRails application server
Web Applicationaccess-analyzerReact frontend
Connector APIaccess-analyzerGo connector execution service
PostgreSQLaccess-analyzerPrimary relational database
ClickHouseaccess-analyzerAnalytics and log storage
Redisaccess-analyzerSession cache and job queues
Metabaseaccess-analyzerEmbedded analytics dashboards
Traefikkube-systemIngress controller and routing
OpenTelemetry Collectoraccess-analyzerObservability data pipeline
Prometheusaccess-analyzerMetrics collection
ArgoCDargocdGitOps application controller

Resource Usage

Monitor node-level resource consumption:

kubectl top nodes
kubectl top pods -A --sort-by=memory

Next Steps