micro--go-micro
Claude
8fa7047bd6
govulncheck / govulncheck (push) Has been cancelled
Harness (E2E) / Harnesses (mock LLM) (push) Has been cancelled
Harness (E2E) / Provider harnesses (live LLM conformance) (push) Has been cancelled
Lint / golangci-lint (push) Has been cancelled
Run Tests / Unit Tests (push) Has been cancelled
Run Tests / Etcd Integration Tests (push) Has been cancelled
The CRD manifests were kept in two places — real YAML under config/crd/ (for kubectl apply) and byte-identical const strings in manifests.go (for the Go CRDManifests map) — which will silently drift. Make config/crd/*.yaml the single source of truth and go:embed it; CRDManifests now reads the embedded bytes. Drops ~120 lines of duplicated YAML, no behavior change (still stdlib-only, tests unchanged). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
Kubernetes deployment foundation (alpha)
This package is the first opt-in Kubernetes foundation for the Go Micro lifecycle:
Service, Agent, and Flow resources. It is intentionally experimental and
additive. Nothing in the Go Micro runtime installs these resources or changes
production defaults.
What is included
- Alpha CRD manifests in
config/crd/foragents.micro.dev,services.micro.dev, andflows.micro.dev. - A small dependency-free mapper that turns a desired Go Micro resource into the
Kubernetes
Deploymentshape an operator reconciliation loop will own. - Unit tests that validate the structural CRD fragments and dry-run the Agent-to-Deployment mapping.
Local validation
go test ./deploy/kubernetes
If you have a Kubernetes cluster and kubectl available, you can also perform a
server-side dry run of the CRDs:
kubectl apply --dry-run=server -f deploy/kubernetes/config/crd/
The manifests are v1alpha1; expect the API shape to evolve before this becomes
a production operator.