jeffryandClaude Opus 5
cc66e227a3
This repository is now the public half of a split: six documents saying what to decide, and one gap. How the cluster is built moved to jeffry/homelab-impl, which is private because its README is an inventory of chart versions and image tags. History starts here deliberately, and not as tidiness. The previous history contained that inventory, and this repository is public — a deletion commit would have removed it from the tree and left it in the log. A fresh root can only carry what is in it. Two pointers rewritten rather than deleted: private-access.md and .loom/README.md both directed a reader to TAILSCALE.md and README.md at the root, which are now private. They now say a fuller reference exists, that it is private, and how to ask — because a public page naming a private thing as its answer is the failure this project has now hit four times. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.0 KiB
Publishing a container image somewhere this cluster can pull it
Every service here runs from an image, and nothing says where our own images come from.
The images currently running are all somebody else's, pulled from public registries. There is no path for an image we build.
Where we looked
This repository — the rebuild steps, the manifests, and every published document. Nothing describes publishing.
What exists and is not finished
The git host has a container registry. It is there. Access to it is not worked out — not the credentials, not who holds them, not how a workload presents them at pull time.
What we are doing instead
Nothing yet. No service here is built from an image we produce, so the gap has not blocked anything. It blocks the first one that is.
Whose job
Probably ours, since the registry is on this cluster — but the credential question is the same one as any other secret a workload needs, and that has no answer here either. Not asserted.