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.

    1. Sync the dependency container images in the addon to your private image registry, the sync command can be as following:
    1. $ docker pull fluxcd/helm-controller:v0.11.1
    2. $ docker push <your repo url>/fluxcd/helm-controller:v0.11.1
    1. Parts of addons may rely on helm charts, e.g. . You should sync these helm charts to your private chart registry.

    1. Modify the values of addon by referring to your own image/chart registry. You can find all images/charts dependency in the files of subdirectory resources/, just modify the configuration. For example, you can modify the fluxcd addon files addons/fluxcd/resources/deployment/helm-controller.yaml the deployment object’s field spec.sepc.containers[0].image to your own image repo.

    1. $ 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.

    There is no need to modify the addon files for enabling this addon, you only need to sync these images and enable this addon with repo args to reference your own registry.

    eg：

    1. Sync the image to your own images registry.
    2. Dowload the terraform helm chart.
    1. $ helm pull https://charts.kubevela.net/addons/terraform-controller-0.3.5.tgz
    1. Extract the chart and modify the values.yaml change image.repository to your own image registry.Then push it to your helm chart museum.