<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Skopeo on Nicolas Massé</title><link>https://www.itix.fr/opensource/skopeo/</link><description>Recent content in Skopeo on Nicolas Massé</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 18 Nov 2019 00:00:00 +0200</lastBuildDate><atom:link href="https://www.itix.fr/opensource/skopeo/index.xml" rel="self" type="application/rss+xml"/><item><title>Airgap OpenShift Installation: move the registry created using oc adm release mirror between environments</title><link>https://www.itix.fr/blog/airgap-openshift-installation-move-registry-created-using-oc-adm-release-mirror-between-environments/</link><pubDate>Mon, 18 Nov 2019 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/airgap-openshift-installation-move-registry-created-using-oc-adm-release-mirror-between-environments/</guid><description>Some customers, especially large banks, have very tight security requirements. Most of them enforce a complete disconnection of their internal networks from the Internet.
When installing OpenShift in such environments (this is named &amp;ldquo;disconnected&amp;rdquo; or &amp;ldquo;airgap&amp;rdquo; installation), all the OpenShift images have to be fetched (thanks to oc adm release mirror) in a dedicated registry from a bastion host that is both on the internal network and on the Internet.</description></item></channel></rss>