Update Center
The optional update center serves the exact Jenkins plugins selected by version profiles. Enable it when controllers must use an in-cluster plugin source, when egress is restricted, or when plugin artifacts need controlled retention.
Enable storage and service
Section titled “Enable storage and service”updateCenter: enabled: true storage: type: local local: size: 10Gilocal uses a PVC. oci stores content in an OCI registry and requires storage.oci.ref; configure storage.oci.existingSecret for private registry access. Local storage runs a single writer. Uploads also require a single writer.
Populate plugins
Section titled “Populate plugins”Choose one or more sources:
| Source | Use |
|---|---|
seed.refs | Import known OCI plugin packs during reconciliation. |
| Pull-through | Fetch missing artifacts from the configured upstream. |
| Upload | Add an .hpi through the authenticated API or CLI. |
| Import | Transfer a plugin pack from an OCI, directory, or tar source. |
varroactl upload plugin <file.hpi>varroactl import --from <source> --to <destination>Enable pull-through only when the update center may reach its configured upstream and archive hosts. In an air-gapped environment, seed or import every required plugin before deploying controllers. See Air-gapped installation and Plugin packs.
Check readiness
Section titled “Check readiness”kubectl get updatecenter varroa-update-centervarroactl get versionprofilesThe update center reports gaps when a pinned plugin is unavailable. Resolve gaps by adding the required artifact or changing the version profile. A member cluster needs its own enabled and populated update center when its controllers cannot reach the core service.