Skip to content

[Automated] Draft docs (kagent): Anthropic Self Hosted Sandboxes - #736

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
pr-tracker-draft-kagent-3521
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
pr-tracker-draft-kagent-3521

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

The target's own content scan fails where the base build passed (docs-theme-extras markdown-leaks / built-html-integrity):

  • markdown-leaks.spec.ts > markdown-leaks: rendered HTML scan > no leaked markdown across built HTML pages

kagent-dev/kagent#3521 — Anthropic Self Hosted Sandboxes

Docs versions: main

No code-path rule covers 11 touched file(s). The planner could route these only by identifier search, so the candidate pages may miss what they changed, including in the other mode:

  • go/README.md
  • go/core/cmd/controller/anthropicselfhostedsandboxes.go
  • go/core/cmd/controller/main.go
  • go/core/internal/anthropicselfhostedsandboxes/collector.go
  • go/core/internal/anthropicselfhostedsandboxes/discovery.go
  • go/core/internal/anthropicselfhostedsandboxes/launcher.go
  • ...and 5 more

What changes for users: Operators can enable an experimental Anthropic self-hosted sandbox launcher by setting EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_* environment variables on the kagent controller. The launcher runs only on the leader controller replica, provisions Sandboxes from a configured SandboxTemplate, and uses controller.terminationGracePeriodSeconds: 180 so accepted launches can drain during shutdown.

What the docs now say: The Operational considerations page now documents the controller environment variables, required SandboxTemplate reference, optional base URL and TTL settings, and the leader-only replica behavior. The installation page was left unchanged because the pull request says install UX is not addressed.

How kagent-3521 was drafted

Plan, and what changed it

  • Planned: Choose between the installation page and the operational considerations page for the new Anthropic self-hosted sandbox controller configuration.
  • Learned: body.md says the feature is configured entirely with environment variables and does not address install UX, while operational-considerations.md already owns controller configuration and controller replica behavior.
  • Did: Added a focused Anthropic self-hosted sandboxes section and the controller.terminationGracePeriodSeconds replica note to operational-considerations.md.

Why a documentation change is necessary

The pull request adds an environment-driven controller launcher for Anthropic self-hosted sandbox work and adds the controller.terminationGracePeriodSeconds Helm value. The generated Helm reference covers the value mechanically, but no prose page explains the required EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_* variables, the leader-only behavior, or why the default grace period matters. The operations page is the right target because it already explains controller configuration and controller replica behavior; setup/installation.md is a fresh-install procedure, and the pull request body says install UX is still not addressed.

How to verify this change

  1. Create a Secret that holds the Anthropic environment key, then install or upgrade kagent with controller.env entries for EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_ENABLED, EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_ENVIRONMENT_ID, EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_ENVIRONMENT_KEY, EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_TEMPLATE_NAMESPACE, and EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_TEMPLATE_NAME.
  2. Check the rendered controller Deployment. kubectl get deployment kagent-controller -n kagent -o jsonpath='{.spec.template.spec.terminationGracePeriodSeconds}' shows 180, and the controller container includes the EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_* environment variables.
  3. Start Anthropic self-hosted work against the configured environment. The leader controller replica claims the work, creates or reuses a Sandbox from the configured SandboxTemplate, and starts ant beta:worker run inside that Sandbox.

Proposed release note

No proposed-release-note.md: markers.notes_placeable is false.

Suggested note text: kagent can now run Anthropic self-hosted sandbox work from the controller. Configure the EXPERIMENTAL_ANTHROPIC_SELF_HOSTED_SANDBOXES_* controller environment variables to enable the launcher and point it at the SandboxTemplate for Anthropic CLI workers.

Files in this pull request

  • docs-site/content/kagent/main/operations/operational-considerations.md
How the pages were chosen (triage report)

New configuration: no page mentions it yet

kagent-dev/kagent#3521 — Anthropic Self Hosted Sandboxes

  • Product: kagent (upstream) → kagent-dev/website
  • Docs version: main
  • Summary (the title; the body has no description): Anthropic Self Hosted Sandboxes
  • Not tested: no cluster was available, so every command in this diff is unrun
  • No rule covers 11 touched file(s). The candidate pages below come from the files that DID match a rule, so they may scope this narrower than the change is. Read these before deciding the change is only about the pages listed:
    • go/README.md
    • go/core/cmd/controller/anthropicselfhostedsandboxes.go
    • go/core/cmd/controller/main.go
    • go/core/internal/anthropicselfhostedsandboxes/collector.go
    • go/core/internal/anthropicselfhostedsandboxes/discovery.go
    • go/core/internal/anthropicselfhostedsandboxes/launcher.go
    • ...and 5 more

Draft branch: pr-tracker-draft-kagent-3521


Important

The test suite has not run on this pull request. It was opened by github-actions[bot], and GitHub does not start workflows for pull requests opened with the repository's own token. This repository's checks are held as action_required until somebody presses Approve and run on the Checks tab. Checks that come from GitHub Apps rather than Actions, such as DCO, run on their own.

Please approve the checks before reviewing the content: an absence of failures here means the tests have not run, not that they passed.

Signed-off-by: GitHub Action <action@github.com>
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.

1 participant