o8 status
Check Orchestr8 platform status and validate prerequisites.
Synopsis
o8 status [OPTIONS]
Description
The status command provides a comprehensive overview of your Orchestr8 platform deployment including:
- Infrastructure Status - Cloud resources and cluster information
- Kubernetes Connectivity - Cluster access and context
- Platform Components - ArgoCD, Keycloak, Istio deployment status
- ArgoCD Applications - Sync and health status of all applications
- Authentication - GitHub repository access configuration
Options
| Option | Short | Description | Default |
|---|---|---|---|
--validate | -v | Only validate prerequisites without checking deployment status | false |
Prerequisites
Examples
Basic Status Check
# Full platform status
o8 status
Prerequisites Validation Only
# Only check prerequisites without deployment status
o8 status --validate
Output Sections
Infrastructure Status (GCP with Terraform)
☁️ Infrastructure (GCP)
Status: Provisioned
Cluster: my-cluster
Project: my-project-123
Region: us-central1
K8s Version: 1.28.3-gke.1286000
Nodes: 6
Cluster Status: RUNNING
Endpoint: https://34.123.45.67
Kubernetes Status
☸️ Kubernetes
Status: Connected
Context: gke_my-project-123_us-central1_my-cluster
ArgoCD Status
🚀 ArgoCD
Status: Installed
URL: http://localhost:30080
Login: admin / [password]
Platform Components
📦 Platform: Deployed
🔐 Keycloak: Running
URL: http://localhost:30081
Login: admin / [password]
Repository Status
📁 Repository: Local Development
No external repository authentication needed
ArgoCD Applications
ArgoCD Applications:
orchestr8-platform: Sync: Synced, Health: Healthy
istio-system: Sync: Synced, Health: Healthy
monitoring: Sync: OutOfSync, Health: Progressing
Status Indicators
Sync Status
- Synced ✅ - Application is up to date with Git repository
- OutOfSync ⚠️ - Application differs from Git repository
- Unknown ❌ - Cannot determine sync status
Health Status
- Healthy ✅ - All resources are running and ready
- Progressing ⚠️ - Resources are deploying or updating
- Degraded ❌ - Some resources are failing
- Unknown ❌ - Cannot determine health status
Exit Codes
| Code | Description |
|---|---|
| 0 | Status check completed successfully |
| 1 | Error checking status or connecting to cluster |
Use Cases
Deployment Verification
# After setup, verify everything is working
o8 setup --provider local
o8 status
Troubleshooting
# Check what's wrong with platform
o8 status
# If issues found, run diagnostics
o8 doctor --verbose
Monitoring
# Regular status checks in scripts
#!/bin/bash
if o8 status --validate; then
echo "Prerequisites satisfied"
o8 status
else
echo "Missing prerequisites"
exit 1
fi
CI/CD Integration
# In deployment pipeline
o8 setup --non-interactive --provider gcp
o8 status
if [ $? -ne 0 ]; then
echo "Platform deployment failed"
exit 1
fi
Provider-Specific Information
Local Development
- Shows localhost URLs for all services
- Indicates local development mode
- No cloud infrastructure information
GCP (with Terraform)
- GKE cluster details and node information
- Project ID and region
- Terraform-managed infrastructure status
- Workload Identity configuration
GCP (without Terraform)
- Detects GKE cluster but shows "not managed by O8"
- Suggests using
--provision-infrastructurefor full management
AWS/Azure
- Shows cluster connectivity
- Manual cluster setup information
- Limited infrastructure details (no automated provisioning)
Troubleshooting
Common Issues
"Not connected to Kubernetes cluster"
# Check kubectl configuration
kubectl config current-context
kubectl cluster-info
# Verify cluster access
kubectl get nodes
"ArgoCD not installed"
# Check if setup was completed
kubectl get namespace argocd
# Re-run setup if needed
o8 setup --provider [your-provider]
"Repository not connected"
# Configure GitHub authentication
o8 auth --github-org your-org
# Or reconfigure during setup
o8 setup --auth-interactive
Related Commands
o8 setup- Initial platform deploymento8 doctor- Comprehensive diagnosticso8 validate- Prerequisites validation onlyo8 apps- Detailed ArgoCD application status