Disconnected

To perform a disconnected deployment, the container images will need to be mirrored within the private organization container registry.
Here is an example using a Google Cloud Platform private container registry:

docker pull ghcr.io/ondat/trousseau:v1.1.3
docker pull vault:1.9.4
docker tag ghcr.io/ondat/trousseau:v1.1.3 us-central1-docker.pkg.dev/shaped-complex-318513/ondat/trousseau:v1.1.3
docker tag vault:1.9.4 us-central1-docker.pkg.dev/shaped-complex-318513/vault/vault:1.9.4
docker push us-central1-docker.pkg.dev/shaped-complex-318513/ondat/trousseau:v1.1.3
docker push us-central1-docker.pkg.dev/shaped-complex-318513/vault/vault:1.9.4

During the installation steps, a DaemonSet will be used to deploy Trousseau on Kubernetes. Along with other parameters, the DaemonSet defines what container images are required and where to get them via the paramters image:.

Here is an extract for the connected installation:

Connected installation

    initContainers:
        - name: vault-agent
        image: vault

    containers:
        - name: trousseau-kms-provider
        image: ghcr.io/ondat/trousseau:v1.1.3

Based on the above container image pushes to a private container image registry, edit the as follow:

Disconnected installation

    initContainers:
        - name: vault-agent
        image: us-central1-docker.pkg.dev/shaped-complex-318513/vault/vault:1.9.4

    containers:
        - name: trousseau-kms-provider
        image: us-central1-docker.pkg.dev/shaped-complex-318513/ondat/trousseau:v1.1.3