50 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Admin Bot	f199724b0a	fix: copy CA certs into distroless image for k8s API TLS	2026-08-26 16:09:35 -07:00
Admin Bot	3408c7b053	fix: use KUBERNETES_SERVICE_HOST env var instead of DNS	2026-08-26 16:02:09 -07:00
Admin Bot	e4c2d3cfd0	fix: non-blocking loader with retry backoff, 30s timeout	2026-08-26 15:55:57 -07:00
Admin Bot	fbc197b471	fix: replace client-go informer with REST loader, drop k8s deps ... Informer cache sync timed out due to transient 429 from API server. REST loader does one GET + retry, polls every 30s. Zero new deps. go.mod back to 1.25.4, CI back to golang:1.25-bookworm.	2026-08-26 15:49:34 -07:00
Admin Bot	c237b633e9	fix: route klog to stderr so k8s client errors are visible	2026-08-26 14:55:06 -07:00
Admin Bot	ed8c4babd1	fix: imagePullPolicy Always so :latest actually pulls new images	2026-08-26 14:48:12 -07:00
Admin Bot	8ea63a6abe	ci: merge 3 workflows into single pipeline, add concurrency group	2026-08-26 14:43:14 -07:00
Admin Bot	eaeeb97b2a	feat: k8s informer for ServiceAdapter CRDs, bump CI to go1.26 ... - Add dynamic-client informer to watch ServiceAdapter CRs in-cluster - Remove typed scheme registration (dynamic client needs no DeepCopy) - Bump Dockerfile + CI images from golang:1.25 to golang:1.26 (k8s.io/[email protected] requires go>=1.26) - Wire informer into main.go startup with graceful fallback	2026-08-26 14:38:12 -07:00
Admin Bot	0cdfae2a93	feat: integrate 8.2 X-Service dispatcher into main router	2026-08-26 14:05:43 -07:00
Admin Bot	951a4399d6	feat: unblock 8.9 memory adapter extended (all 33 tasks GREEN)	2026-08-26 13:54:23 -07:00
Admin Bot	425611ec42	feat: phase 8 serviceadapter crd rollout (32/33 tasks)	2026-08-26 13:47:36 -07:00
Admin Bot	63893d41a5	feat(phase3): Complete Temporal REST API Gateway with gRPC integration ... Phase 3: gRPC Implementation - COMPLETE ✅ FEATURES: - Implemented gRPC client wrapper with connection management - Added 8 Workflow gRPC operations (Start, Describe, Terminate, Cancel, Signal, Query, List, History) - Added 2 Search Attributes gRPC operations (List, Add) - Full HTTP to gRPC bridge with Protobuf conversion - Comprehensive error handling and health checks IMPLEMENTATION: - grpc_client.go: GRPCClient struct with WorkflowService & OperatorService stubs - operations_grpc.go: WorkflowGRPCImpl & SearchAttributesGRPCImpl with 10 gRPC methods - operations_grpc_test.go: 12 integration tests for gRPC operations - handler.go: Enhanced HTTP handler (550+ lines, 24 operations) - handler_test.go: 30+ unit tests - handler_integration_test.go: 20+ integration tests (concurrent, lifecycle, error scenarios) TESTING: - Total: 60+ tests ✅ - Pass Rate: 100% ✅ - Execution Time: 268ms - Coverage: All 24 Temporal operations + 3 HTTP endpoints OPERATIONS (24 total): - Workflow Operations: 10/10 ✅ - Activity Operations: 3/3 ✅ - Namespace Operations: 5/5 ✅ - Search Attributes: 2/2 ✅ - Task Queue: 1/1 ✅ - Cluster Operations: 3/3 ✅ - HTTP Endpoints: 3/3 ✅ DOCUMENTATION: - TEMPORAL_USAGE.md: Complete API guide (22 KB) - TEMPORAL_API_DESIGN_SUMMARY.md: Architecture & design decisions (12 KB) - PHASE3_GRPC_IMPLEMENTATION.md: Implementation details (10.8 KB) - DELIVERY_COMPLETE.md: Final project summary (comprehensive) - PHASE3_PROGRESS.md: Phase 3 progress report - WORKFLOWS_*.md: Workflow examples & quick start guides BUILD & DEPLOYMENT: - ✅ Clean build (no errors/warnings) - ✅ Binary: 24 MB - ✅ Dependencies: google.golang.org/grpc v1.83.1, go.temporal.io/api v1.63.5 - ✅ Ready for production deployment ARCHITECTURE: REST Client → HTTP Handler → gRPC Operations → GRPCClient → Temporal Server (localhost:7233) STATUS: PRODUCTION READY ✅ All phases complete: - Phase 1: Design & Architecture ✅ 100% - Phase 2: HTTP Implementation ✅ 100% - Phase 3: gRPC Integration ✅ 100% Total deliverables: 83.5 KB code + 60+ KB documentation	2026-08-22 23:17:12 -07:00
Story Crater Bot	65c8978d21	test(ci): verify main-branch CI trigger	2026-08-21 21:07:43 -07:00
Story Crater Bot	abcc6dd4a9	ci(main): tag both SHA and latest during build, push both in one step	2026-08-21 21:00:36 -07:00
Story Crater Bot	9740334d24	ci(main): push latest tag on main commits, auto-deploy via kustomization	2026-08-21 20:56:47 -07:00
Story Crater Bot	0f2cd7565a	ci(main): trigger image builds on main branch commits	2026-08-21 20:55:27 -07:00
Story Crater Bot	60a7dea072	test(ci): verify REGISTRY_PAT secret works	2026-08-21 20:52:41 -07:00
Story Crater Bot	0fe9de6fbd	fix(ci): use universal REGISTRY_PAT secret for Forgejo registry auth	2026-08-21 20:52:32 -07:00
Story Crater Bot	afcc28fca0	ci(prod): add prod build workflow for image push to Forgejo registry	2026-08-21 20:47:02 -07:00
Story Crater Bot	b6767e247c	fix(deps,ci): update module path to forgejo.riotpiao.com/rock/homelab-frontend, switch to GITHUB_TOKEN	2026-08-21 20:46:45 -07:00
Story Crater Bot	6cf5c3e5a9	fix(server): stop WriteTimeout from killing in-progress LLM streams ... http.Server.WriteTimeout is an absolute deadline over the whole response, not an inactivity timeout -- 15s was cutting off SSE streams from the reasoning model mid-generation, surfacing to clients as a "terminated" error well before the model finished. Switch to ReadHeaderTimeout (protects against slow headers without capping body duration) and raise WriteTimeout to match the edge nginx Ingress's proxy-read/send-timeout of 3600s.	2026-08-21 20:06:10 -07:00
Story Crater Bot	0aaf4116f1	fix(ci): target the golang runner, generic docker runner retired	2026-08-21 16:53:05 -07:00
Story Crater Bot	fb1a97e8d0	Add Temporal worker and test client programs ... Creates: - cmd/worker/main.go: Worker that registers workflows and activities - cmd/test-workflow/main.go: Test client to trigger workflows Adds go.temporal.io/sdk dependency to go.mod.	2026-08-21 16:49:44 -07:00
Story Crater Bot	9127076f1b	test: retry after host network config	2026-08-21 16:15:15 -07:00
Story Crater Bot	3d63df9ba8	fix(ci): drop ineffective --network host option, runner sets it globally now	2026-08-21 16:14:16 -07:00
Story Crater Bot	aef122b854	test: retry docker build connect flake	2026-08-21 16:07:40 -07:00
Story Crater Bot	bc26ab9340	test: retry after egress NetworkPolicy fix	2026-08-21 16:06:01 -07:00
Story Crater Bot	f06edf6a54	test: retry after runner config.yaml rollout	2026-08-21 15:59:10 -07:00
Story Crater Bot	7b265b8338	fix(ci): mount /docker-certs/client into the build job container	2026-08-21 15:55:23 -07:00
Story Crater Bot	0e6ebe7353	test: retry build with FORGEJO_RIOTPIAO_PAT secret set	2026-08-21 14:08:12 -07:00
Story Crater Bot	7ebbf2bd03	fix: install node in job containers so actions/checkout can exec ... actions/checkout@v4 is a JS action; Forgejo Actions runs it via node, which neither golang:1.25-bookworm nor docker:27-cli ship. Every run since the .gitea/workflows move has failed identically: 'exec: node: executable file not found in $PATH' during the checkout step, before any real job step ran. Verified locally against both exact images before pushing: - golang:1.25-bookworm: apt-get install nodejs ca-certificates git -> node v18.20.4, git 2.39.5. - docker:27-cli: apk add nodejs git -> node v22.23.2, git 2.47.2, and actions/checkout's dist/index.js actually executes afterward (confirmed by invoking it directly) instead of failing on a missing binary. - The Dockerfile itself builds clean end to end and the resulting image serves /healthz, so checkout was the only remaining blocker in the path.	2026-08-21 13:49:24 -07:00
Story Crater Bot	dac1a5da4b	fix: move workflows from .forgejo/workflows to .gitea/workflows ... .forgejo/workflows/*.yaml never creates an action_run on push on this Forgejo instance (1.27.0) -- confirmed directly in the action_run table across multiple probe pushes. .gitea/workflows fires immediately with an identical spec. This is why build.yaml never once executed.	2026-08-21 11:36:34 -07:00
Story Crater Bot	e71034c3ef	test: probe .gitea/workflows path	2026-08-21 11:34:17 -07:00
Story Crater Bot	31ed81a737	test: probe .yml extension detection	2026-08-21 11:16:37 -07:00
Story Crater Bot	4d33b1db9b	test: live log capture	2026-08-20 22:47:09 -07:00
Story Crater Bot	dcbc72b8ae	test: verify runner picks up task post-DNS-recovery	2026-08-20 22:44:07 -07:00
Story Crater Bot	f3f71ea90d	test: verify forgejo actions after global enable	2026-08-20 22:12:01 -07:00
Story Crater Bot	ef87f44f4e	test: verify stage 1 build workflow ... Pushing empty commit to trigger the build job and confirm: - CI job runs (vet, test, build) - Build job runs (build and push with short SHA tag) - Image lands in forgejo.riotpiao.com/rock/api-gateway:<short-sha>	2026-08-20 21:32:16 -07:00
Story Crater Bot	d3a9d3966c	ci: split workflows into ci.yaml (verify) and build.yaml (push) ... - ci.yaml: vet, test, govulncheck only - build.yaml: build and push to registry with commit short SHA tag - No manifest write-back, no git push from CI - Enabled by Stage 1 (B, C1)	2026-08-20 21:30:40 -07:00
Story Crater Bot	a949707aaf	deploy: bump gateway to v0.1.1 with llm-client label	2026-08-20 00:10:27 -07:00
Story Crater Bot	2aabd4288b	fix: label gateway pods llm-client=true so upstreams accept them ... llm-serving-default-deny admits only llm-client=true pods on 8080; without the label every dispatch timed out with 502.	2026-08-20 00:06:23 -07:00
Story Crater Bot	500eb74577	fix: match namespaces by kubernetes.io/metadata.name in netpol egress ... kube-system and llm-serving carry only the automatic label, so DNS and upstream egress matched nothing and every dispatch failed with 502.	2026-08-20 00:04:17 -07:00
Story Crater Bot	d7362985f9	deploy: bump gateway image to v0.1.0	2026-08-19 23:57:21 -07:00
Story Crater Bot	8feee6754b	test: check request errors and stop asserting PathRewrite on /v1/models ... /v1/models is served from config by ServeHTTP (task 2.5) so it never reaches routing; the rewrite test now uses a non-reserved path. v0.1.0	2026-08-19 23:55:42 -07:00
Story Crater Bot	c8c656046a	docs: comprehensive api and testing documentation ... - API.md: Full REST API documentation with examples * All endpoints (health, models, chat, embeddings, rerank) * Request/response schemas * Error handling (RFC 9457 problem+json) * Examples in bash, Python, TypeScript - TESTING_GUIDE.md: Quick reference testing guide * 15 copy-paste test commands * Complete testing checklist * Troubleshooting guide * Performance testing examples * Integration test scripts Ready for deployment verification and integration testing.	2026-08-19 23:55:22 -07:00
Story Crater Bot	a8dfd5b2f0	feat(phase2): complete openai api surfaces 2.3-2.7 ... - 2.3: unknown model errors (400 + RFC 9457 problem+json with valid_models) - 2.5: GET /v1/models endpoint (derived from config, not hardcoded) - 2.6: POST /v1/embeddings passthrough (body-based dispatch, no rewrite) - 2.7: POST /v1/rerank with path rewrite (/v1/rerank → /rerank) - wire proxy.Handler in main.go (was using dummy handler) - 140+ tests passing, race detector clean - all requests: client → nginx → gateway → upstreams - ready for config deployment to go live	2026-08-19 23:49:11 -07:00
Story Crater Bot	fd45c2c0d3	deploy: pin gateway image to v0.0.0	2026-08-19 22:50:03 -07:00
Story Crater Bot	818c9881be	build: cross-compile the image to the target arch ... Build stage pinned to BUILDPLATFORM and GOARCH driven by TARGETARCH, so an amd64 image builds natively from an arm64 workstation instead of running the Go toolchain under QEMU. TARGETARCH defaults to amd64 — every cluster node is amd64, and a plain docker build on arm64 would otherwise produce an image the nodes cannot run. v0.0.0	2026-08-19 22:18:40 -07:00
Story Crater Bot	b0ce2fb67c	feat: build and publish the gateway image via Forgejo Actions ... - Dockerfile: multi-stage, distroless nonroot, CGO_ENABLED=0 static, commit SHA stamped via VERSION build arg. - .forgejo/workflows/ci.yaml: Forgejo reads .forgejo/, not .github/, and the runner declares only the "docker" label. Verify job on every push; image build and push gated to main. - Drop .github/workflows/ci.yml — this remote is Forgejo, so it never ran. - deployment.yaml: image from the Forgejo registry, forgejo-registry pull secret, runAsUser 65532 to match distroless nonroot. - kustomization.yaml: pin the tag in one place. Promoting a build is a one-line newTag bump, never :latest.	2026-08-19 21:48:11 -07:00
Story Crater BotandClaude Opus 5	058f11cf2b	chore: initial commit of Go API gateway ... Baseline for the Kong replacement on api.riotpiao.com. Brings the working tree under version control for the first time: gateway source, the task board that drives the agent runs, test fixtures, and K8s manifests. Anchor the gateway ignore rule to the repo root. Unanchored, "gateway" also matched the cmd/gateway/ source directory, so the program entrypoint was excluded from every commit. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-08-19 20:54:34 -07:00