[FEATURE] Ship a self-contained air-gapped kagent + Substrate install bundle

未关闭
  • 哪里不对？
#2,932 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
helm, kubernetes
领域
cloud, devops, infrastructure

调研方向

Start by reviewing the Substrate-enabled Helm chart and its SandboxConfig, worker image, and asset-fetch tracking issue #1855. Define the versioned chart, image, gVisor asset, checksums or digests, and internal source, then run the proposed air-gap acceptance test with public egress denied: install, create a SandboxAgent, reach a Ready ActorTemplate with a golden snapshot, and start an actor on a new node.

由索引模型根据 Issue 内容生成。

描述

Feature summary

Provide a versioned, self-contained offline deployment path for kagent SandboxAgents using Agent Substrate. The install artifacts should include the pinned gVisor runtime asset, so a cluster does not need to fetch it from public Google Storage when an actor starts.

Problem statement / motivation

We are evaluating kagent 0.10.1 with Agent Substrate 0.0.9 in network-isolated Kubernetes environments, including AKS and GCP. Mirroring the Helm chart and container images is not sufficient for the Substrate-backed path: its SandboxConfig points to a public gs://gvisor runsc binary, while the ateom-gvisor worker image does not contain that binary. On a cold node, the runtime attempts an asset fetch. Public storage egress is not available or permitted in these environments.

The older kagent air-gap issue #228 covers mirroring the chart and images, but not this separately fetched runtime asset. The related private-registry image issue #2055 is also a different layer.

Proposed solution

Please provide a supported, versioned offline install bundle or equivalent reproducible export/import process for the minimal Substrate-enabled SandboxAgent path. It should cover the Helm chart and dependencies, required container images, the exact pinned gVisor asset, checksums or digests, and configuration for an internal registry or asset source.

The runtime asset could be included in the worker image or installed through a kagent-managed mechanism, provided new and replacement nodes are ready without a manual per-node pre-seed. Installation and actor start must make no request to public Google Storage or other public artifact endpoints. If the underlying asset-fetch capability must change in Substrate, please consume and expose that fix in the kagent release and chart; upstream tracking is https://github.com/agent-substrate/substrate/issues/1855.

An air-gap acceptance test would import the published artifacts into an internal registry, deny public egress, install the Substrate-enabled chart, create a SandboxAgent, reach a Ready ActorTemplate with a golden snapshot, and verify an actor can start on a newly added node without an external fetch.

Alternatives considered

We tested packaging the pinned runsc binary in an internally mirrored image and using a DaemonSet to seed the atelet cache on every eligible node. It works, but adds a separately maintained node setup step and must cover replacements and version changes. A supported bundled path would remove that operational requirement.

Additional context

Sanitized evaluation and workaround: https://github.com/davidmarkgardiner/kagent-public/blob/main/work-agent-bundles/agent-substrate/RUNSC-AIRGAP-ROADMAP-QUESTION.md

Is a self-contained, no-public-fetch Substrate-enabled install on the kagent roadmap? If a newer kagent release already provides it, which artifacts and configuration should we use?

主要语言
Go
星标
4.2k
派生
890
平均合并
1 天 6 小时
30 天内合并 PR
189

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

kagent-dev/kagent 的其他 Issue

查看 kagent-dev/kagent 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。