-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
None
-
Strategy to complete installations where there isn't a pre-existing registry
-
False
-
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-283 - Deploy OpenShift without external registry in disconnected environments
-
80% To Do, 0% In Progress, 20% Done
-
XL
Epic Goal
As an OpenShift installation administrator I must install OCP clusters in green-field environments where there isn't a pre-existing image registry. I need the installation process to include a registry that permits the cluster to install and run.
I may optionally need additional content in the registry (operators, image streams).
Why is this important?
A common use case for agent-based deployments is a disconnected environment, where a registry needs to be mirrored in a location accessible to the clusters to be installed.
BILLI requires a registry that exists before the clusters can be installed. It is common to not have one in the environment and having to create it as part of the installation of the first cluster in an environment.
BILLI's goal is to make the installation as easy as possible while keeping the flexibility provided by UPI installations. Streamlining the installation of the registry along with the OpenShift installation is necessary to deliver BILLI's expected user experience.
Previous Work
- OCP Orchestrated Disconnected Updates
- bjozsa's PoC: https://gist.github.com/v1k0d3n/cbadfb78d45498b79428f5632853112a
- oc-mirror plug-in GA in 4.11
Update March 2023
As a result of this work during the 4.13 cycle an OpenShift enhancement has been published for reviews:
OpenShift Enhancement: https://github.com/openshift/enhancements/pull/1352
- is related to
-
-
- New
-
- relates to
-
RFE-2617 Mitigate or eliminate the requirement of an external registry on isolated environments
-
- Backlog
-
1.
|
Docs Tracker |
|
To Do | 
|
Unassigned |
2.
|
PX Tracker |
|
To Do |
|
Unassigned |
3.
|
QE Tracker |
|
To Do |
|
zhenying niu |
4.
|
TE Tracker |
|
To Do |
|
Unassigned |
