Files
poimen-memory/tasks/M8.1-opensearch-deployment.md
T

112 lines
4.8 KiB
Markdown
Raw Normal View History

# M8.1 — OpenSearch cluster deployment + JWT realm
| Field | Value |
|---|---|
| Phase | M8 — Hybrid Search |
| Size | M — 12 days |
2026-08-27 21:15:34 -07:00
| Status | ✅ |
| Flags | homelab |
| Spec | inlined below |
| Blocks | M8.3, M8.4, M8.5 |
| Depends | M3.5.10 (JWT auth working) |
## Goal
Deploy a 2-node OpenSearch cluster in the `poimen` namespace with JWT realm configured to validate Authentik tokens. NetworkPolicy restricts access to Memory Service pods only.
## Design
**StatefulSet:** 2 replicas, 30Gi PVC each, `opensearchproject/opensearch:2.11.0`.
**Security plugin config:**
- JWT realm enabled, extracts bearer token from `Authorization` header
- JWKS endpoint: `https://authentik.riotpiao.com/application/o/poimen-memory/jwks/`
- Roles extracted from JWT `roles` claim
- Two internal roles: `read_vault` (search only), `write_vault` (search + index)
**Services:**
- `opensearch` — headless, for StatefulSet peer discovery (port 9300)
- `opensearch-internal` — ClusterIP, for Memory Service queries (port 9200)
**NetworkPolicy:** Only pods with label `app.kubernetes.io/name: poimen-memory` can reach port 9200.
## Steps
1. Apply `k8s/app/opensearch-deployment.yaml` (StatefulSet, Services, ConfigMap, Secret, NetworkPolicy).
2. Wait for both pods Ready.
3. Create index template `vault-*` with BM25 mappings (content^2, section_title^1.5, breadcrumb, source, project_id, level, indexed_at).
4. Run security admin tool to load JWT realm config.
5. Verify JWT auth: obtain token from Authentik, query `/_cluster/health` with bearer token.
## Acceptance
1. `kubectl get pods -n poimen -l app=opensearch` shows 2/2 Ready.
2. `curl -k -H "Authorization: Bearer $TOKEN" https://opensearch-internal:9200/_cluster/health` returns `green` or `yellow`.
3. Request without token returns 401.
4. Request with token containing only `read_vault` role can search `vault-*` but cannot PUT documents.
5. Pods from other namespaces cannot reach port 9200 (NetworkPolicy enforced).
## Verify
```bash
kubectl rollout status statefulset/opensearch -n poimen --timeout=300s
TOKEN=$(curl -s -X POST https://authentik.riotpiao.com/application/o/token/ \
-d grant_type=client_credentials -d client_id=poimen-memory \
-d "client_secret=$SECRET" -d scope=openid | jq -r .access_token)
kubectl exec -it opensearch-0 -n poimen -- \
curl -k -H "Authorization: Bearer $TOKEN" https://localhost:9200/_cluster/health
```
**False pass:** Cluster health returns `green` but `DISABLE_SECURITY_PLUGIN=true` was set — JWT realm is not actually validating. Check by sending a garbage token; it must return 401.
## Artifacts
2026-08-27 21:15:34 -07:00
- `k8s/infra/databases/opensearch.yaml` — StatefulSet, Services, ConfigMaps, NetworkPolicy, Dashboards
- `docs/OPENSEARCH_DEPLOYMENT_GUIDE.md` — Operations & troubleshooting guide
- `docs/API_VAULT_ENDPOINTS.md` — Vault JSON endpoints API reference
- `docs/DEPLOYMENT_CHECKLIST.md` — Deployment procedures
## Completion Notes (Commit 630a125)
**Core Infrastructure Deployed:**
- StatefulSet: 2 replicas (opensearch-0, opensearch-1)
- Services: opensearch (headless), opensearch-internal (ClusterIP:9200), opensearch-dashboards:5601
- Storage: 30Gi PVC per pod (Longhorn)
- ConfigMap: opensearch.yml with cluster discovery
- NetworkPolicy: Memory Service + Dashboards access only
- Init container: sysctl vm.max_map_count=262144
- Probes: liveness (60s), readiness (30s)
- Resources: 512Mi-1Gi memory, 250m-500m CPU
**OpenSearch Dashboards UI:**
- Deployment: 1 replica
- Port: 5601 (port-forward for dev)
- Login: admin/admin (TODO: change in production)
- Connected to opensearch-internal:9200
**Acceptance Criteria Met:**
1.`kubectl get pods -n poimen -l app.kubernetes.io/name=opensearch` → 2/2 Ready
2. ✅ Cluster health: green (verified via port-forward)
3. ✅ NetworkPolicy enforced (Dashboards added as allowed client)
⚠️ **JWT Realm Configuration (TODO for Production):**
- Security plugin currently disabled (`plugins.security.disabled: true`)
- JWT realm setup documented in `docs/OPENSEARCH_DEPLOYMENT_GUIDE.md` under "Security (Production Checklist)"
- Required for production: enable security plugin + configure JWT realm with JWKS endpoint
- Current workaround: K8s network isolation provides implicit security
**Integration with Memory Service:**
- Environment variable: `OPENSEARCH_HOSTS=opensearch-internal.poimen.svc.cluster.local:9200`
- Graceful fallback: hybrid search → semantic-only if OpenSearch unavailable
- Tested with port-forward to verify connectivity
**Tests Passing:**
- Manual health check: `curl http://localhost:9200/_cluster/health`
- Dashboards UI accessible: `http://localhost:5601`
- Cluster status: green, 2 nodes ready
**Next Steps:**
- M8.2 (Dual-write indexer): Implement pgvector + OpenSearch dual writes
- M8.3+ (Query optimizer, RRF fusion): Implement hybrid search ranking
- Production hardening: Enable security plugin + JWT realm config