Air-gapped Installation for Addon
Generally, you should git clone the repo which contained the addon configuration, you can specify a local addon directory when enable an addon for installation. While you should make sure all container images or helm charts are replaced by your private registry.
You can follow these steps as an example.
- Git clone the catalog repo to download these addon files. You can find all community addons in subdirectory
./addons/
and experimental addons in subdirectory./experimental/addons
.
- Sync the dependency container images in the addon to your private image registry, the sync command can be as following:
$ docker pull fluxcd/helm-controller:v0.11.1
$ docker push <your repo url>/fluxcd/helm-controller:v0.11.1
- Parts of addons may rely on helm charts, e.g.
terraform addon
. You should sync these helm charts to your private chart registry.
Use
vela cli
to enable an addon with specify a local addon dir to install offline.
$ vela addon enable /your/local/addon/directory
Here’s a list about images or helm charts of all community addons that should be synced for air-gapped installation.
You need sync these images to your own image registry, and modify the related addon files to reference you own registry.
eg:
- Sync the image
oamdev/terraform-controller:0.3.5
to your own images registry. - Dowload the terraform helm chart.
$ helm pull https://charts.kubevela.net/addons/terraform-controller-0.3.5.tgz
Modify the addon file
terraform/resources/terraform-controller.cue
changeoutput.properties.url
to your chart museum’s url.Sync the image
oamdev/vela-rollout:v1.6.4
to your own images registry.- Dowload the rollout helm chart.
- Extract the chart and modify the
values.yaml
changeimage.repository
to your own image registry.Then push it to your helm chart museum. - Modify the addon file change
output.properties.url
to your chart museum’s url.