Meta tags:
description=Container Registries at the Edge;

Headings (most frequently used words):

to, air, harbor, from, cloud, gap, same, community, project, one, registry, workflow, edge, tool, why, satellite, join, the, central, ground, control, regional, dc, factory, floor, telco, pop, retail, store, vehicle, single, board, device, classified, sites, ships, ot, networks, process, just, media, break, reliability, security, fleet, management, gapped, ready, cri, integration, lightweight, cncf, slack, github, documentation,

Text of the page (most frequently used words):
the (26), harbor (20), #satellite (17), and (14), same (13), with (11), air (11), edge (9), fleet (8), site (8), #registry (7), gap (6), project (5), cncf (5), images (5), process (5), gapped (5), signed (5), live (5), sync (5), community (4), github (4), slack (4), single (4), oci (4), image (4), across (4), groups (4), from (4), separate (4), bundle (4), join (3), for (3), cri (3), sites (3), differential (3), bundles (3), local (3), disk (3), replication (3), them (3), network (3), record (3), policy (3), only (3), that (3), source (3), part (2), blog (2), container (2), view (2), binary (2), layout (2), minimal (2), footprint (2), byo (2), mirror (2), k3s (2), replicated (2), content (2), distribution (2), assign (2), management (2), spiffe (2), spire (2), trust (2), identity (2), security (2), each (2), location (2), when (2), reliability (2), every (2), central (2), identical (2), last (2), state (2), stays (2), delivery (2), classified (2), one (2), whole (2), transport (2), not (2), second (2), workflow (2), you (2), ground (2), control (2), media (2), break (2), regional (2), factory (2), floor (2), truth (2), once (2), cloud (2), get (2), started (2), 2026, contributors, license, architecture, quickstart, installation, overview, introduction, documentation, extends, learn, more, about, broader, repository, star, repo, report, issues, contribute, channel, questions, discussions, support, connect, oras, backed, resource, constrained, environments, lightweight, configure, containerd, docker, podman, use, upstream, fallback, deliver, straight, into, rke2, integration, import, temporarily, disconnected, keep, their, resume, reconnect, ready, centrally, manage, hundreds, locations, group, satellites, zero, automatic, credential, rotation, static, secrets, shipped, devices, are, prepositioned, persistent, storage, they, stay, goes, down, extend, your, why, sequence, chain, rejects, skipped, replayed, resumes, automatically, known, recovery, while, online, zone, never, connects, ship, sea, remote, mine, link, outage, example, full, temporary, solution, keeps, spectrum, detail, other, tools, make, build, pipeline, packaging, inventory, produces, place, carry, verifies, imports, consistent, reconnects, picks, applied, just, changes, ships, networks, offline, tolerant, through, direct, retail, store, vehicle, board, device, small, kubernetes, continuous, workload, telco, pop, big, define, policies, signing, keys, core, how, reach, property, product, tool, continuum, runs, everywhere, whether, data, center, rack, all, delivers, however, can, receive, open, docs,

Text of the page (random words):
harbor satellite harbor satellite docs blog github get started open source one registry workflow from cloud to edge to air gap harbor satellite runs the same image distribution process everywhere whether that s a regional data center a rack on a factory floor or a site with no network at all assign images once satellite delivers them however each site can receive them get started view on github the registry continuum same tool from cloud to air gap every site is a satellite in the same fleet how images reach it live sync or a signed bundle is a property of the site not a separate product harbor core central harbor ground control define groups policies and signing keys once the single source of truth for the whole fleet source of truth big edge regional dc factory floor telco pop satellite on kubernetes with continuous replication and spiffe spire workload identity live sync small edge retail store vehicle single board device single binary with an oci image layout on local disk minimal footprint cri mirror through a byo registry or direct delivery to k3s live sync offline tolerant air gapped classified sites ships ot networks same satellite record same groups same policy only the transport changes signed bundle across a media break air gapped same process just a media break other air gap tools make you build a second pipeline with separate packaging separate inventory and separate trust with harbor satellite an air gapped site is the same satellite in the same fleet ground control produces a signed differential oci bundle in place of a live sync you carry it across the satellite verifies and imports it and the site s state stays consistent with the fleet when the site reconnects replication picks up from the last applied bundle harbor satellite is the only registry solution that keeps one process across the whole spectrum the air gap is a transport detail not a second workflow temporary air gap full air gap example ship at sea remote mine link outage classified network ot zone that never connects delivery live sync while online replicated content stays on local disk signed differential bundles only recovery resumes automatically from the last known state sequence chain rejects skipped or replayed bundles process identical same fleet record groups and policy identical same fleet record groups and policy why harbor satellite extend your container registry to every edge location with reliability security and central management reliability images are prepositioned in persistent storage at each edge location so they stay on site when the network goes down security spiffe spire zero trust identity with automatic credential rotation no static secrets shipped to edge devices fleet management centrally manage image distribution across hundreds of edge locations group images and assign them to satellites air gapped ready same fleet same process air gapped sites import signed differential oci bundles temporarily disconnected sites keep their replicated content on local disk and resume replication on reconnect cri integration configure containerd docker cri o and podman to use an edge byo registry as a mirror with upstream fallback or deliver images straight into k3s and rke2 lightweight single binary with an oras backed oci image layout minimal resource footprint for constrained edge environments join the community harbor satellite is part of the harbor cncf project connect with us cncf slack join harbor satellite on the cncf slack for questions discussions and support join slack channel github star the repo report issues and contribute to harbor satellite view repository harbor project harbor satellite extends the harbor container registry learn more about the broader project harbor community documentation introduction blog overview installation quickstart architecture community cncf slack github harbor community project license harbor cncf 2026 harbor satellite contributors part of the harbor project