feat: the registry is registry.dataverket.org; Flux and Zitadel models; registry credential in the vault #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "registry-and-flux-models"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Registry
zot runs in
dataverket-prodatregistry.dataverket.org(flux-bootstrap #2-#4, delivered gitless). Everyregistry.dataverket.internal(Makefile,.forgejo/workflows/release.yaml,workflow-fabrikk-release.yaml, delivery skill, README) now saysregistry.dataverket.org. The README follow-up list records what is left for the release runner.Credential
fabrikk-ciis owned by the cluster repo (artifacts/zot/zot-ci-credentials.enc.yaml) and copied into thefabrikkvault asregistry/ci_username/registry/ci_password, per the standard: the cluster repo owns, the factory copies.Models
@ginger_pappa/flux;dataverket-prod-helmis the HelmRelease model for the cluster (contextdataverket-prod-admin, wraps the pinnedflux, run with_tools/binon PATH).extensions/models/flux_reset.tsaddsreset(reconcile with--reset). Used once already: the cert-manager release had beenfailedsince its first install timed out on 2026-09-09; after the reset helm-controller upgraded to v2, Ready, no pod restarted. Unit test passes (deno test, run in a container; deno is not installed on the workbench).@thomas/zitadel; no model yet, it waits for a service-user key in the vault.Protected paths touched:
skills/delivery/SKILL.md,Makefile,.forgejo/.