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:
| Status | Meaning |
|---|---|
Running | Pod is active and healthy |
Completed | One-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:
| Field | Expected Value |
|---|---|
| SYNC STATUS | Synced |
| HEALTH STATUS | Healthy |
ArgoCD UI
Access the ArgoCD web interface for a visual overview of all applications:
-
Start port forwarding:
kubectl port-forward svc/argocd-server -n argocd 8090:443 -
Open
https://localhost:8090in a browser -
Retrieve the admin password:
kubectl -n argocd get secret argocd-initial-admin-secret \-o jsonpath='{.data.password}' | base64 -d; echo -
Sign in with username
adminand 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:
| Component | Namespace | Type |
|---|---|---|
| Core API | access-analyzer | Rails application server |
| Web Application | access-analyzer | React frontend |
| Connector API | access-analyzer | Go connector execution service |
| PostgreSQL | access-analyzer | Primary relational database |
| ClickHouse | access-analyzer | Analytics and log storage |
| Redis | access-analyzer | Session cache and job queues |
| Metabase | access-analyzer | Embedded analytics dashboards |
| Traefik | kube-system | Ingress controller and routing |
| OpenTelemetry Collector | access-analyzer | Observability data pipeline |
| Prometheus | access-analyzer | Metrics collection |
| ArgoCD | argocd | GitOps application controller |
Resource Usage
Monitor node-level resource consumption:
kubectl top nodes
kubectl top pods -A --sort-by=memory
Next Steps
- Create your first admin account and sign in
- Configure a data source and run your first scan
- Review install commands for ongoing application management