-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
False
-
-
-
-
-
1. Proposed title of this feature request
Mitigate or eliminate the requirement of an external registry on isolated environments
2. What is the nature and description of the request?
We need a way to install a cluster in an isolated environment in which a host external to the cluster with a repository is not needed. In limited environments like telco where deployments of clusters or SNO can be isolated from the outside and uncleanly rebooted (sometimes both things go together) and in which the number of hosts or resources goes to the minimum needed, reducing this dependency is necessary
3. Why does the customer need this? (List the business requirements here)
An unclean reboot in a disconnected environment without access to the external registry will make the cluster absolutely unbootable as there are dependencies on images even to start crio service.
Also, the certificed operators downloaded though OLM tend to use a pull-polixy=always
4. List any affected packages or components.
- Installer
- Documentation
- Rhcos
- Crio
- OLM
- is related to
-
AGENT-262 Strategy to complete installations where there isn't a pre-existing registry
- To Do
- links to