Home » DevOps » Deploying Che 7 with custom images (air gap environment)

About Nick Boldt

Nick Boldt

Deploying Che 7 with custom images (air gap environment)

Number 5: deploying Che 7 behind a firewall (air gap environment) using chectl –che-operator-cr-yaml=…

Deploying Che 7 with custom images

Unlike  Deploying Che 7 to Minishift 1.34+, this doc will explain how to do an Eclipse Che 7 deployment with a custom resource yaml file to override the images used in the deployment.

This process can be used for many things, but in this example it’ll be in support of an  air gap environment, where an organization cannot directly see Quay or Red Hat Container Catalog, and must instead reference internally mirrored artifacts within their organization’s firewall.


You need the latest  Minishift and n chectl releases.

Fetch them like this (or similar):

cd ~/bin
curl -sSL https://github.com/che-incubator/chectl/releases/download/20190724230954/chectl-linux -o chectl
chmod +x chectl
cd /tmp
curl -sSL https://github.com/minishift/minishift/releases/download/v1.34.1/minishift-1.34.1-linux-amd64.tgz -o minishift.tgz
tar xvzf minishift.tgz
mv minishift*/minishift ~/bin/
chmod +x ~/bin/minishift


  1. Start up minishift. (See Start up Minishift for some suggested default settings.)
    minishift start
  2. Log in once startup is complete.
    oc login 192.168.MY.IP:8433 -u system -p admin
  3. For Eclipse Che 7, pull  these images and  publish them to your internal registry:
    • eclipse/che-server:nightly
    • eclipse/che-keycloak:nightly
    • quay.io/eclipse/che-devfile-registry:nightly
    • quay.io/eclipse/che-plugin-registry:nightly
    • centos/postgresql-96-centos7:latest
    • registry.access.redhat.com/ubi8-minimal:8.0
  4. Create a custom resource file, which overrides the default image values from  che-operator defaults.go to use your custom registry’s images.


    To watch the events and verify which images are pulled, see 
    this post before performing the next step.

  5. Deploy Che to minishift using the custom resource file created above. In this example the namespace che-op is used instead of the default  che:
    chectl server:start -a operator -p minishift \
      --che-operator-cr-yaml=che7-custom-resource-airgap.yaml -n che-op


    If you use the minishift addon to deploy Che (which uses a deployment configuration instead of an operator), your custom resource file will not be used. The addon is deprecated.

  6. You should see this:

    Once deployed, you should see these in your Minishift console: 

    The custom image reference can be seen in the yaml for the deployment:

    Published on System Code Geeks with permission by Nick Boldt, partner at our SCG program. See the original article here: Deploying Che 7 with custom images (air gap environment)

    Opinions expressed by System Code Geeks contributors are their own.

(0 rating, 0 votes)
You need to be a registered member to rate this.
Start the discussion Views Tweet it!
Do you want to know how to develop your skillset to become a sysadmin Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. Introduction to NGINX
2. Apache HTTP Server Cookbook
3. VirtualBox Essentials
4. Nagios Monitoring Cookbook
5. Linux BASH Programming Cookbook
6. Postgresql Database Tutorial
and many more ....
I agree to the Terms and Privacy Policy
Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Inline Feedbacks
View all comments