Kubernetes Quick Start

Turn on Kubernetes and verify the cluster

1. Open Docker Desktop > Settings > Kubernetes
2. Check Enable Kubernetes
3. Click Apply & Restart — wait for the green indicator

# Verify context
kubectl config current-context
# Expected: docker-desktop

# Verify cluster
kubectl cluster-info
# Expected: Kubernetes control plane is running at https://127.0.0.1:6443

Add real Azure AD and Stripe keys for full portal login

The deploy script works out of the box with stub values — all services start and API endpoints work. For real Azure AD sign-in and Stripe payments:

cp .env.local.example .env.local
# Edit .env.local with your Azure AD app registration and Stripe test keys

Without .env.local, the portal UI loads but Azure AD sign-in won’t work. API endpoints function normally with the X-Tenant-ID header.

One command deploys the entire platform

./scripts/deploy-local.sh

This builds Docker images for all 25 services + portal, creates the cloudhealthoffice namespace, deploys MongoDB and Redis, creates all Kubernetes secrets, seeds demo data, and deploys all microservices using the same k8s manifests as production.

First run: ~10–15 minutes (image builds). Subsequent runs: ~2 minutes.

Watch the rollout

In a separate terminal:

watch kubectl get pods -n cloudhealthoffice

All pods should reach Running / 1/1 Ready within 2–3 minutes after images are built.

Port-forward to access services locally

Services run inside the cluster on ClusterIP. Use port-forwarding to reach them (open each in a separate terminal, or append & to background):

# Portal (Blazor Server UI)
kubectl port-forward -n cloudhealthoffice svc/portal 8080:80

# Core API services
kubectl port-forward -n cloudhealthoffice svc/claims-service 5001:80
kubectl port-forward -n cloudhealthoffice svc/benefit-plan-service 5002:80
kubectl port-forward -n cloudhealthoffice svc/member-service 5003:80
kubectl port-forward -n cloudhealthoffice svc/provider-service 5004:80
kubectl port-forward -n cloudhealthoffice svc/eligibility-service 5005:80
kubectl port-forward -n cloudhealthoffice svc/payment-service 5006:80

# MongoDB (for direct access)
kubectl port-forward -n cloudhealthoffice svc/mongodb 27017:27017

Run the full claims lifecycle end-to-end

After port-forwarding Claims (5001) and Benefit Plan (5002):

CLAIMS_URL=http://localhost:5001 \
BENEFIT_URL=http://localhost:5002 \
./scripts/seed-local.sh --tenant demo

This seeds NCCI edits, creates a benefit plan, submits a claim, runs adjudication, executes a payment batch, and downloads an 835 ERA file — the complete claims lifecycle.

For a step-by-step walkthrough with individual curl commands, see the Docker Quick Start guide (steps 3–7 work identically after port-forwarding).

Check pod status and health endpoints

# All pods
kubectl get pods -n cloudhealthoffice

# All services
kubectl get svc -n cloudhealthoffice

# Portal logs
kubectl logs -n cloudhealthoffice -l app=portal --tail=50

# Claims service logs
kubectl logs -n cloudhealthoffice -l app=claims-service --tail=50

# Find errors across all services
kubectl logs -n cloudhealthoffice --all-containers --tail=20 | grep -i error