🤖 CoderWorkspacePool: per-user pools whose owner is the person

未关闭
#455 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
go, kubernetes
领域
backend

调研方向

This is design work, so start by reading the plan referenced in the issue: workspace-13.md section 12 (decision D2) and section 16 item 1. Those sections explain why the owner rules refuse OIDC, GitHub and privileged-role logins, and what the per-user pool model would require. Done means a written decision on relaxed owner rules and per-user pool cost, agreed with maintainers, before any implementation.

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

描述

Idea

Pools whose owner is the person who uses the workspaces, so each person gets ready workspaces of their own instead of a pool owner's shared ones (decision D2, option D).

Why deferred

The owner rules refuse a person's login types (OIDC, GitHub) and privileged roles, because every start build hands the owner's token to the template. Per-user pools need looser owner rules and cost one pool per person. Reserve and Share mode shipped instead.

Plan workspace-13.md section 12 (D2) and section 16 item 1.

Refs #153


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: xhigh

主要语言
Go
星标
5
派生
3
平均合并
1 小时 50 分钟
30 天内合并 PR
160

环境准备

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

从这里开始

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

coder/coder-k8s 的其他 Issue

查看 coder/coder-k8s 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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