🤖 CoderWorkspacePool: strategy Prebuilds after an upstream per-preset count API

Abierto
#459 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go, kubernetes

Línea de trabajo

This is blocked upstream and is not a first-timer task. Read the feasibility comment at coder/coder-k8s#153 and sections 2, 12 and 16 of plan workspace-13.md to see why. Nothing should be built until Coder ships a runtime per-preset count API, and the draft upstream proposal must not be posted without owner approval. Done means the blocker is cleared and a design is agreed with the maintainer.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Idea

spec.strategy: Prebuilds for CoderWorkspacePool: let a pool size a Coder prebuild preset instead of building its own workspaces (Design A). The value is reserved, and version 1 accepts only Managed.

Blocked upstream

Coder has no API that changes a preset's prebuild count without a new template version, and a new version rebuilds every prebuild of the template. See the feasibility result in https://github.com/coder/coder-k8s/issues/153#issuecomment-5964210861. Recheck trigger: a Coder release with a runtime per-preset count API.

Requirements when it unblocks

  • Prebuilds are a Premium feature, so the controller must check the license: GET /api/v2/entitlements returns workspace_prebuilds, usable when enabled is true and the entitlement is entitled or grace_period (#153).
  • The upstream API proposal in the comment above is a draft. Decision D11 is not approved: the repository owner approves any post outside this repository. Nothing is posted upstream.

Plan workspace-13.md sections 2 and 12 (D1, D11) and section 16 item 5.

Refs #153


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

Lenguaje dominante
Go
Estrellas
5
Forks
3
Merge medio
2 h 49 min
PR fusionados (30 d)
206

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de coder/coder-k8s

Todos los issues de coder/coder-k8s

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.