Air-gapped installations
Weik.io 2026.2An air-gapped installation pulls its images from your own registry and resolves every Camel dependency through one Maven mirror.
On this page
Weik.io builds each version of an integration once, at the hub, so the agents never resolve anything themselves. For an air-gapped installation, give the first weikio-backend init your own registry for the images and your Maven mirror for Camel’s dependencies.
What leaves the hub#
Every image of the stack is pinned by digest and pulled from the registry you give at install, which is Docker Hub unless you give another. Apart from the registry, the hub connects out only to the systems you set up. In an air-gapped installation, keep them inside your network:
- The Maven repositories that builds resolve from
- The certificate authority and the DNS provider behind the hub’s certificates
- The bucket the backup copies go to
- A Dapr secrets sidecar, when you use an external secret store
- The systems the telemetry forwarder sends to, when you apply a forwarding configuration
- Your identity provider, when people sign in through one
Replace the Maven repositories with one mirror, and replace the certificate authority and the DNS provider as Certificates without public DNS says.
The hub never connects to a Git repository, because your pipelines push changes to Weik.io with the weikio CLI. An agent connects only to the hub on port 443, and to the registry in its bundle when you install or upgrade the agent.
Images from your registry#
- Mirror every image that
images.envlists into your registry, and keep the upstream paths. - Check the release’s
images.envandSHA256SUMSas in any install. - Set
IMGto the backend image in your registry. - Run
initwith your registry in--registry.
The init command also sets your Maven mirror and leaves out Maven Central:
$ docker run --rm -u 1654:1654 -v /opt/weikio:/opt/weikio -e WEIKIO_HOME=/opt/weikio -e Weikio__Keys__Dir=/opt/weikio/keys \
-e WEIKIO_MASTER_KEY_FILE=/opt/weikio/master.key -e Weikio__Nats__Urls__0=nats://nats:4222 -e WEIKIO_BACKEND_IMAGE=$IMG \
$IMG weikio-backend init --public-base-url https://acme.example --public-leaf-url wss://nats.acme.example:443 --disk-budget 40GiB \
--registry registry.acme.example \
--maven-repository corp=https://maven.acme.example/repository/all,mirror --no-maven-centralAfter init, the stack’s .env has WEIKIO_REGISTRY near the top, above the image lines that an upgrade writes again. upgrade.sh pulls the release’s backend image from your registry too.
Each agent pulls its images from the registry that its bundle’s .env sets in WEIKIO_REGISTRY.
Maven through one mirror#
An agent fetches each built version over its link to the hub and needs no other path out of its network. The hub gets the jars of each version from the Maven repositories that init sets:
| Flag | What it does |
|---|---|
-- |
Adds a repository that builds may resolve from |
,mirror after the URL |
Marks the repository that mirrors everything |
-- |
Leaves Maven Central out |
Repeat --maven-repository for each repository. Without any --maven-repository, builds use Maven Central and Atlassian’s public repository. The repositories you give replace Atlassian’s, but Maven Central stays until you add --no-maven-central.
After init, add a repository’s credentials to the hub’s configuration. Put the user name there as plain text. Put the password in a project secret, which you create with weikio secret set <project>/<name> and refer to as <project>.<name>. Keep that secret in a project you never delete, such as a separate platform project.
Give Weik.io a repository account that can only read, because a build can read the credentials in its Maven settings.
A build runs isolated and can make TCP connections to any address, but only on the ports of the Maven repositories that Weik.io is set up with. Keeping integrations apart describes the isolation.
Certificates without public DNS#
A hub with no public DNS can’t get its certificates from Let’s Encrypt over the internet. To have the platform’s certificate authority sign the hub’s names, give the first init the flag --hub-names-authority platform. The agents then trust the hub with no further steps, because every agent’s bundle has the authority’s certificate. Add --authority-names to limit that authority to your suffixes, such as corp.example,factory.local. A certificate authority of your own that speaks ACME works too, as Certificates describes.
The CLI in a closed network#
The install script downloads the weikio CLI from weik.io and checks it against the release’s SHA256SUMS. In a closed network, copy the CLI’s release folder to a server of your own and give the script the folder’s address in WEIKIO_CLI_DOWNLOADS_URL.