https://www-staging.alwaldend.com/docs/infra/harbor/ Recent content in harbor on Alwaldend Hugo en https://www-staging.alwaldend.com/docs/infra/harbor/openspec/specs/infra-harbor/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/infra/harbor/openspec/specs/infra-harbor/spec/ <h1 id="harbor-infrastructure-specification">Harbor infrastructure specification<a class="td-heading-self-link" href="#harbor-infrastructure-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Describe the Harbor registry infrastructure owned by <code>infra/harbor</code>, spanning Proxmox setup, K3s host configuration, Flux-managed chart declarations, and Harbor service Terraform. The <code>tf_setup</code>, <code>ansible</code>, <code>cl</code>, and <code>tf</code> packages are implementation stages of this owner. This is a checked-in source baseline, without an observation of live registry availability or deployment success.</p> <p>Baseline revision: <code>550d7e79b1f5fdbc2b6017b75178471d6914082f</code>. Observed: 2026-09-08. Sources: <a href="https://www-staging.alwaldend.com/docs/infra/harbor/">owner README</a>, <a href="../../../BUILD.bazel">BUILD</a>, and the implementation links below.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-dedicated-k3s-registry-host">Requirement: Dedicated K3s registry host<a class="td-heading-self-link" href="#requirement-dedicated-k3s-registry-host" aria-label="Heading self-link"></a></h3><p>Setup SHALL declare a Proxmox VM in the <code>src_infra_harbor</code> pool with two cores, 4096 MiB memory, and 20 GiB boot, 20 GiB K3s data, and 40 GiB K3s storage disks. Ansible SHALL apply the shared host and K3s roles with K3s secrets encryption enabled. Its firewall variables SHALL scope API port 6443 access to the declared Flux host address.</p> https://www-staging.alwaldend.com/docs/infra/harbor/openspec/specs/owned-dns/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/infra/harbor/openspec/specs/owned-dns/spec/ <h1 id="owned-dns-specification">owned-dns Specification<a class="td-heading-self-link" href="#owned-dns-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Define Harbor DNS management through the owner&rsquo;s <code>tf_setup</code> root, including canonical declarations, scoped credentials, and offline source checks before adopting live records.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-owner-local-dns-configuration">Requirement: Owner-local DNS configuration<a class="td-heading-self-link" href="#requirement-owner-local-dns-configuration" aria-label="Heading self-link"></a></h3><p>The <code>tf_setup</code> root SHALL consume this owner&rsquo;s canonical <code>dnsconfig.json</code> through the shared DNS Terraform module, preserving declared record identities and views. DNS resources SHALL default to disabled before adoption and SHALL default to enabled in the reviewed adoption revision and after adoption. Adoption SHALL import the exact existing provider records and require a scoped no-change import plan before saved-plan apply. Subsequent reconciliation with unchanged root inputs SHALL preserve adopted records, unrelated DNS records, and non-DNS resources in the root.</p>