🤖 CoderWorkspacePool: keep the pool owner active with its own token

未關閉
#456 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
8/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
go, kubernetes

研究方向

The issue names no source files, tests or entry points; it points to plan workspace-13.md (sections 12 and 16), which the payload does not include. Before any code, read that plan and the D7 decision to learn which owner credential is stored in the Secret and how the pool checks eligibility. The work needs a security review first, so a newcomer should not start a patch. Done would mean a recorded decision on the token design, not an implementation.

由索引模型根據 Issue 內容生成。

描述

Idea

Keep a pool owner active with the owner's own token, stored in a Secret (decision D7, option C). Today Coder marks an owner dormant after 90 days without a login or API use, and the pool then stops with OwnerNotEligible and deletes its unclaimed workspaces. The admin must use the owner's credentials at least once every 90 days.

Why deferred

A credential Secret for the owner needs its own security review. Option B (the activate route) was refused, because it can also lift a suspension.

Plan workspace-13.md section 12 (D7) and section 16 item 2.

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 摘要。