Using Sonatype Nexus as a generic proxy registry to deploy OpenShift
( or much I dislike arbitrary limitations ) Red Hat Openshift Red Hat Openshift (OCP) is a superb container platform, but a few things in that ecosystem have bugged me since the start for my homelab. Quay.io has limits/throttling in place to limit things that can be downloaded/mirrored in a given timeframe. Most literature around disconnected installs revolves around Using Red Hat Quay as -the- registry and involves a semi-manual way to mirror a -specific- OCP release. Those DMZ quays have to be pre-populated with content/versions to be able to support any OCP disconnected installs. What if I wanted to: be able to do 10-15 OCP deploys in a single day without hitting quay.io's download limits? be able to deploy OCP 4.16.25 and two hours later deploy OCP 4.8.z-latest or OCP 4.19-RC3 on another system in Lab just a few minutes later? be able to avoid taking down the family's Internet when I deploy OCP? minimize manual steps involved (no more manual pre-mirroring involved)? be abl...