Skip to content

docs(k8s): align AgentTeams orchestration guide - #1039

Open
RerankerGuo wants to merge 1 commit into
agentscope-ai:mainfrom
RerankerGuo:docs/k8s-guide-agentteams-contract
Open

docs(k8s): align AgentTeams orchestration guide#1039
RerankerGuo wants to merge 1 commit into
agentscope-ai:mainfrom
RerankerGuo:docs/k8s-guide-agentteams-contract

Conversation

@RerankerGuo

Copy link
Copy Markdown
Contributor

Summary

  • Update the English and Chinese Kubernetes-native orchestration guides to use the AgentTeams project name throughout.
  • Align operational examples with current container names, AGENTTEAMS_* image variables, agentteams.io API group, local gateway domains, and repository URL.
  • Document QwenPaw (runtime: qwenpaw) and CoPaw (runtime: copaw) as distinct current runtimes while preserving intentional hiclaw CLI, installer, chart, release, and Helm resource names.

Why

The AgentTeams hard cut updated runtime and deployment contracts, but these architecture guides still mixed the old brand with retired Embedded container names, environment variables, API group, gateway domains, and repository links. Several examples therefore pointed readers at values that current installs no longer create or accept.

Verification

  • Compared the documented contracts with the Worker CRD, controller backend/config, installer, Helm chart metadata, and chart helpers.
  • Confirmed no open PR modifies either guide.
  • Parsed both Worker YAML examples with Ruby 2.7.
  • go test ./internal/backend ./internal/config
  • Checked stale contracts, bilingual key coverage, relative links, balanced code fences, and git diff --check.

Refs #958

@shiyiyue1102

shiyiyue1102 commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

The documentation corrections are useful, but the standalone value of this PR is limited and it overlaps the same AgentTeams runtime-contract cleanup in #1037 and #1038. Please consolidate #1037-#1039 into one current documentation-contract PR, or clearly explain why they must remain independently mergeable. In either case, refresh the diff against the latest main branch and drop lines that are already correct after the recent rename and release changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants