Air gap configuration
Learn how to install Cobrowse Enterprise with an air gap configuration, isolated from public internet and untrusted local networks.
Last updated
Was this helpful?
Learn how to install Cobrowse Enterprise with an air gap configuration, isolated from public internet and untrusted local networks.
Last updated
Was this helpful?
Cobrowse Enterprise can be installed with an air gap configuration, isolated from public internet and untrusted local networks.
This document contains the extra steps you will have to take to ensure your installation works in an isolated network.
Cobrowse is distributed using docker container images. You will need to pull these images and make them available within the isolated network. There are some options available to accomplish this:
Use a and use docker push
to populate its images
Use a
By default, the Cobrowse Enterprise helm chart references repository ghcr.io/cobrowseio
to fetch images. After making your images available internally, you can override the image.repo
helm value to change the repository images are pulled from. For example:
If your internal docker repository requires credentials, you should manage your own docker pull credentials using kubernetes' standard dockerconfigjson
functionality.
Please consult your docker registry documentation for what values should be used for the docker server, username, password and email address.
Cobrowse requires a MongoDB-compatible database for storing its data. You will need to install a MongoDB (or compatible, such as AWS DocumentDB) database accessible from your isolated network.
To manage your own credentials, first ensure you do not set an imageCredentials.password
helm value in your deployment. Then you should create a standard kubernetes docker registry secret named cobrowse-docker-cfg
(replace cobrowse
with your helm release name if you've changed it) with your registry credentials. Instructions on how to do this is using kubectl
are located in the . For example: