Remove stale TinyLlama deploy artifacts #60

New issue

Closed

opened 2026-05-23 20:54:35 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:54:35 +00:00

Owner

Originally filed by @coilysiren on 2026-05-10T05:34:58Z - https://github.com/coilysiren/infrastructure/issues/107

The llama namespace is referenced across the repo but was never deployed to the cluster (kubectl get all -n llama returns empty, llama not in kubectl get ns). The TinyLlama-1.1B manifest is a relic from an earlier exploration.

Local-model worker tier work (LUCA Mode 1/2) will start from a fresh design once GPU feasibility on kai-server is settled. Keeping stale infra-as-code around just causes confusion.

Files to remove:

llama/deploy.yml (the manifest itself)
src/llama.py (Invoke tasks for deploy)
Reference in tasks.py (import + add_collection)
Mentions in README.md, docs/architecture.md, docs/FEATURES.md

_Originally filed by @coilysiren on 2026-05-10T05:34:58Z - [https://github.com/coilysiren/infrastructure/issues/107](https://github.com/coilysiren/infrastructure/issues/107)_ The `llama` namespace is referenced across the repo but was never deployed to the cluster (`kubectl get all -n llama` returns empty, `llama` not in `kubectl get ns`). The TinyLlama-1.1B manifest is a relic from an earlier exploration. Local-model worker tier work (LUCA Mode 1/2) will start from a fresh design once GPU feasibility on kai-server is settled. Keeping stale infra-as-code around just causes confusion. Files to remove: - ``llama/deploy.yml`` (the manifest itself) - ``src/llama.py`` (Invoke tasks for deploy) - Reference in ``tasks.py`` (import + add_collection) - Mentions in ``README.md``, ``docs/architecture.md``, ``docs/FEATURES.md``

coilysiren referenced this issue

2026-05-26 05:23:02 +00:00

Monitoring #131

coilysiren added the

priority

label

2026-06-04 08:16:55 +00:00

coilysiren commented

2026-06-17 08:22:49 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:22:49 +00:00

closed this issue
added the
burndown-2026-06
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/infrastructure#60

No description provided.

Rows
Columns