chore: migrate CR group refs to the 3-group *.nanohype.dev taxonomy#20
Merged
Conversation
Replace the single `agents.stxkxs.io` CR group with the locked per-kind
taxonomy on the `nanohype.dev` domain. The API version stays `v1alpha1`
across all three groups:
- platform.nanohype.dev — Tenant, Platform
- agents.nanohype.dev — AgentFleet, ModelGateway, AgentSandbox, SandboxPool
- governance.nanohype.dev — BudgetPolicy, EvalSuite
─── Code ───
- src/k8s.ts: drop the single `AGENTS_GROUP` constant in favour of a
`CRD_GROUP_BY_KIND` map plus `groupForKind(kind)` and
`apiVersionForKind(kind)` resolvers, with a `CrdKind` union covering
the eight mapped kinds. Both call sites resolve their group through the
map: `getPlatform` reads `platform.nanohype.dev`, the AgentSandbox path
reads `agents.nanohype.dev`.
- src/runtimes/sdk-k8s.ts: the dispatched `AgentSandbox` manifest builds
its `apiVersion` via `apiVersionForKind('AgentSandbox')` →
`agents.nanohype.dev/v1alpha1`, so the wire group tracks the map.
─── Deploy RBAC ───
- deploy/rbac.yaml: fab's dispatch Role touches two CRD kinds that now
live in different groups, so the single `agents.stxkxs.io` rule splits
into `agents.nanohype.dev` (agentsandboxes — create/get/list/watch/delete)
and `platform.nanohype.dev` (platforms — get).
─── Standards + contract ───
- src/standards.ts: PLATFORM_TENANT_CONTRACT and IAC_BY_TARGET prose name
the Platform CR as `platform.nanohype.dev/v1alpha1` and the AgentFleet CR
as `agents.nanohype.dev/v1alpha1`.
- src/standards/platform-tenant-contract.json: the `platform_cr_shape`
apiVersion becomes `platform.nanohype.dev/v1alpha1`.
─── Skills + role prose ───
- skills/eks-agent-platform-curation.md: the "API group" line documents
all three groups; the Platform example uses `platform.nanohype.dev`, the
AgentFleet example uses `agents.nanohype.dev`.
- skills/kagent-curation.md: the runtime kinds (Agent, AgentTool,
AgentSkill) move to `agents.nanohype.dev`; the prose notes Platform CRDs
now live in `platform.nanohype.dev`.
- skills/agentgateway-curation.md: the AgentRoute and ModelEgress examples
move to `agents.nanohype.dev` (agent-traffic kinds alongside ModelGateway).
- skills/kubebuilder-engineering.md: the `operator-sdk create api` example
scaffolds PlatformQuota under `platform.nanohype.dev` (a Platform quota
override).
- src/team/build/agent-platform.ts: the eks-agent-platform-curator brief
describes the `*.nanohype.dev/v1alpha1` surface across the three groups.
- .plans/k8s-first-standards.md: the Platform CR reference reads
`platform.nanohype.dev/v1alpha1`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the single
agents.stxkxs.ioCR group with the locked per-kind taxonomy on thenanohype.devdomain. API version staysv1alpha1across all three groups.platform.nanohype.devagents.nanohype.devgovernance.nanohype.devWhat changed
Code
src/k8s.ts— the singleAGENTS_GROUPconstant becomes aCRD_GROUP_BY_KINDmap withgroupForKind/apiVersionForKindresolvers and aCrdKindunion. Call sites resolve per kind:getPlatform→platform.nanohype.dev, the AgentSandbox path →agents.nanohype.dev.src/runtimes/sdk-k8s.ts— the dispatchedAgentSandboxmanifest builds itsapiVersionviaapiVersionForKind('AgentSandbox')→agents.nanohype.dev/v1alpha1.Deploy RBAC
deploy/rbac.yaml— fab's dispatch Role touches two kinds now in different groups, so the rule splits intoagents.nanohype.dev(agentsandboxes) andplatform.nanohype.dev(platforms).Standards + contract
src/standards.ts,src/standards/platform-tenant-contract.json— Platform CR →platform.nanohype.dev/v1alpha1, AgentFleet CR →agents.nanohype.dev/v1alpha1.Skills + role prose
skills/eks-agent-platform-curation.md,skills/kagent-curation.md,skills/agentgateway-curation.md,skills/kubebuilder-engineering.md,src/team/build/agent-platform.ts,.plans/k8s-first-standards.md— YAML examples and prose moved to the per-kind groups (kubebuilderPlatformQuotaexample scaffolds underplatform.nanohype.dev).Verification
CI gate green from a clean install:
npm run build— cleannpm run lint(typecheck + eslint) — cleannpm test— 257 passed (21 files)npm run format:check— clean