Skip to main content
AI
  • Get started with AI

    • Red Hat AI

      Accelerate the development and deployment of enterprise AI solutions.

    • AI learning hub

      Explore learning materials and tools, organized by task.

    • AI interactive demos

      Click through scenarios with Red Hat AI, including training LLMs and more.

    • AI/ML learning paths

      Expand your Red Hat OpenShift AI knowledge using these learning resources.

    • AI quickstarts

      Focused AI use cases designed for fast deployment on Red Hat AI platforms.

    • No-cost AI training

      Foundational Red Hat AI training.

  • Featured resources

    • Red Hat OpenShift AI
    • Open source AI for developers
    • AI product application development
    • Open source-powered AI/ML for hybrid cloud
    • AI and Node.js cheat sheet

Red Hat AI Factory with NVIDIA

Red Hat AI Factory with NVIDIA is a co-engineered, enterprise-grade AI solution for building, deploying, and managing AI at scale across hybrid cloud environments.

Learn
  • Self-guided

    • Documentation

      Find answers, get step-by-step guidance, and learn how to use Red Hat products.

    • Learning paths

      Explore curated walkthroughs for common development tasks.

    • Guided learning

      Receive custom learning paths powered by our AI assistant.

    • See all learning
  • Hands-on

    • Developer Sandbox

      Spin up Red Hat's products and technologies without setup or configuration.

    • Interactive labs

      Learn by doing in these hands-on, browser-based experiences.

    • Interactive demos

      Click through product features in these guided tours.

  • Browse by topic

    • AI/ML
    • Automation
    • Java
    • Kubernetes
    • Linux
    • See all topics
  • Training & certifications

    • Courses and exams
    • Certifications
    • Skills assessments
    • Red Hat Academy
    • Learning subscription
    • Explore training
Build
  • Get started

    • Red Hat build of Podman Desktop

      A downloadable, local development hub to experiment with our products and builds.

    • Developer Sandbox

      Spin up Red Hat's products and technologies without setup or configuration.

  • Download products

    • Red Hat Enterprise Linux
    • Red Hat AI
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products
  • Featured

    • Red Hat build of OpenJDK
    • Red Hat JBoss Enterprise Application Platform
    • Red Hat OpenShift Dev Spaces
    • Red Hat Developer Toolset
  • References

    • E-books
    • Documentation
    • Cheat sheets
    • Architecture center
Community
  • Get involved

    • Events
    • Live AI events
    • Red Hat Summit
    • Red Hat Accelerators
    • Community discussions
  • Follow along

    • Articles & blogs
    • Developer newsletter
    • Videos
    • Github
  • Get help

    • Customer service
    • Customer support
    • Regional contacts
    • Find a partner

Join the Red Hat Developer program

Download Red Hat products and project builds, access support documentation, learning content, and more.

ConsoleDocsSupport Search
New For you

Recommended

We'll recommend resources you may like as you browse. Try these suggestions for now.

  • Product downloads
  • Cheat sheets
  • Red Hat Developer learning portal
  • Developer blog
  • E-books
  • Developer Sandbox
Log in

Get more with a Red Hat Developer account

  • Product downloads
  • Console access
  • Event registration
  • Training & trials
Explore more account benefitsLog in or register

A subscription may be required for some services.

Contact us

Red Hat OpenShift 3.11 disconnected installation using Satellite Docker registry

<p>&nbsp;</p> <quillbot-extension-portal></quillbot-extension-portal>

April 8, 2019
Mohammad Ahmad
Related topics:
ContainersKubernetes
Related products:
Red Hat OpenShiftRed Hat OpenShift Container Platform

    In this article, I will discuss the prerequisites and requirements for the successful implementation of Red Hat OpenShift 3.11 disconnected installation using Red Hat Satellite as the local Docker registry, which I have been able to do with the support of my colleagues. I also discuss adjustments that may be required post install.

    This work is based on the following references:

    • OpenShift disconnected installation documentation
    • Using Satellite 6 Server for a Disconnect OpenShift Container Platform Install

    Prerequisites

    Required Images

    Before starting the installation, you must have all the required Docker images synchronized and accessible from all your nodes.

    You will not need to synchronize all the images (total 100+), and depending on your requirements you will need:

    • Red Hat OpenShift Container Platform infrastructure component images, which are required for your base install, a total of 55 images
    • Red Hat OpenShift Container Platform component images for the optional components, which are required for logging and monitoring, a total of 26 images
    • Red Hat-certified Source-to-Image (S2I) builder images, which are required for your OpenShift applications, a total of 29 images

    Additionally, if you know exactly which images your installation requires (by checking all the Docker images you have on an existing environment), you can pre-synchronize only those images.

    Determine Red Hat OpenShift 3.11 version

    At the time of this installation, version 3.11.69 was used; however, you should install the latest version available for the bugfixes and features.

    This should be reflected in your inventory as follows:

    openshift_release: v3.11
    openshift_image_tag: v3.11.69
    openshift_pkg_version: -3.11.69

    Red Hat Satellite settings

    On the Red Hat Satellite server, create a product within the organization that your Red Hat OpenShift nodes will be registered to

    hammer product create --name "ocp311" --organization "MyOrg"

    Then, you will need to create a repository for each image. This is what makes Red Hat Satellite behave slightly differently from other registries, as Red Hat Satellite will synchronize this image with the upstream server (registry.redhat.io), including all its versions. For example, to create a product for openshift3/ose-node, use the following command:

    hammer repository create --name "openshift3/ose-node" --content-type "docker" --url "http://registry.redhat.io/" --docker-upstream-name "openshift3/ose-node" --product "ocp311" --organization "MyOrg"

    Once you have created all the repositories, you can either synchronize using the GUI or via the command line:

    hammer product synchronize --name "ocp311" --organization "MyOrg"

    Ensure you add the product to the content view that your OpenShift will be registered to access.

    The Red Hat Satellite server implements a Docker registry slightly differently from traditional Docker registries. This means the URL of a Docker image will change from:

    registry.redhat.io/openshift3/ose-pod:v3.11.69

    to

    satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-pod:v3.11.69

    If you do not tell the Red Hat OpenShift installer about this change, the installation will fail. I will provide further instructions in the next section.

    Test an image pull:

    docker pull satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-pod:v3.11.69

    Red Hat OpenShift Ansible inventory modifications

    For the installer to be able to use the Docker registry on Red Hat Satellite, restructure oreg_url as following:

    oreg_url: satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-${component}:${version}
    openshift_disable_check: "docker_image_availability"
    openshift_docker_insecure_registries: "satellite.mydomain:5000"
    openshift_docker_additional_registries: "satellite.mydomain:5000"
    openshift_examples_modify_imagestreams: True

    Set oreg_test_url to false:

    oreg_test_login: false

    Ensure oreg_auth values are commented out. Because no authentication is required, not commenting them out will cause issues:

    # oreg_auth_user: '' # our registry doesn't require authentication. 
    # oreg_auth_password: '' # our registry doesn't require authentication.
    

    Additional inventory variables:

    openshift_examples_registryurl: "{{ oreg_url | default(openshift_hosted_images_dict[openshift_deployment_type]) }}"
    registry_host: "{{ openshift_examples_registryurl.split('/')[0] if '.' in openshift_examples_registryurl.split('/')[0] else '' }}"

    Also, the pattern "MyOrg-ocp311-openshift3_ose-${component}:${version} will not work for etcd; therefore, you must specify the exact etcd docker image URL:

    osm_etcd_image: satellite.mydomain:5000/MyOrg-ocp311-rhel7_etcd:3.2.22

    Post-installation configuration

    Depending on which applications you want to use in your OpenShift cluster, you may want to modify your image streams accordingly. I will not delve into these details here. However, certain tasks may still attempt to pull images from the online registry to perform their functions, such as diagnostics.

    Therefore, to run diagnostics, the following images can be retagged to "trick" diagnostics so it doesn't attempt to pull the image from the online registry:

    ansible nodes --timeout=120 -m shell -b -a 'docker pull satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-deployer:v3.11.69'
    ansible nodes --timeout=120 -m shell -b -a 'docker tag satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-control-plane:v3.11.69 registry.redhat.io/openshift3/ose-control-plane:v3.11.69'
    ansible nodes --timeout=120 -m shell -b -a 'docker tag satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-control-plane:v3.11.69 registry.redhat.io/openshift3/ose-control-plane:v3.11'
    
    ansible nodes --timeout=120 -m shell -b -a 'docker pull satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-node:v3.11.69'
    ansible nodes --timeout=120 -m shell -b -a 'docker tag satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-node:v3.11.69 registry.redhat.io/openshift3/ose-node:v3.11.69'
    ansible nodes --timeout=120 -m shell -b -a 'docker tag satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-node:v3.11.69 registry.redhat.io/openshift3/ose-node:v3.11'
    
    ansible nodes --timeout=120 -m shell -b -a 'docker pull satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-deployer:v3.11.69'
    ansible nodes --timeout=120 -m shell -b -a 'docker tag satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-deployer:v3.11.69 registry.redhat.io/openshift3/ose-deployer:v3.11.69'
    ansible nodes --timeout=120 -m shell -b -a 'docker tag satellite.mydomain:5000/MyOrg-ocp311-openshift3_ose-deployer:v3.11.69 registry.redhat.io/openshift3/ose-deployer:v3.11'
    

    Then, you should be able to run:

    oc adm diagnostics

    Conclusion

    To get your cluster installed in a disconnected mode, the instructions in this article should get you started. However, it may be possible to encounter a missing image or a reference to an online image depending on which applications you might be using. In that case, keep an eye out for such possibilities and consider updating the references in the deployment or build configuration of the application, or re-tagging Docker images as a temporary measure only (just to rule out the error being the image is not reachable).

    Last updated: January 12, 2024

    Recent Posts

    • A day in the life of an NVIDIA H100 on Red Hat OpenShift 5

    • Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install

    • Run Red Hat Enterprise Linux CoreOS on NVIDIA BlueField DPUs

    • Agent harness engineering: Separating model capabilities from enforcement

    • What's new for developers in Red Hat Enterprise Linux 10.3 and 9.9

    Red Hat Developers logo

    Platforms

    • Red Hat AI
    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products

    Build

    • Developer Sandbox
    • Developer tools
    • Interactive tutorials
    • API catalog

    Quicklinks

    • Learning resources
    • E-books
    • Cheat sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site status dashboard
    • Report a security problem

    Red Hat Developer

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2026 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility
    Ask AI