1. Proposed title of this feature request
embed ocp release manifests images into cluster

2. What is the nature and description of the request?
When ocp cluster is power reset or reboot abnormal, during next start, ocp will erase all local container images, and re-pull the ocp release manifest images from quay.io or local mirrors. This is ok for connected cluster, or cluster with local registry mirrors. But under some business senario, especially disconnected edge cluster, which is no local registry mirrors, due to server number limited, so when ocp cluster power reset, the cluster can not start again.

Base on a SE ( https://issues.redhat.com/browse/SUPPORTEX-11008 ), we find out that we can embed the ocp release manifest image into the ocp cluster with a internal registry service. This SE includes a prototype custormer solution and QE has tested it and pass the test.

3. Why does the customer need this? (List the business requirements here)
This RFE can benifies every openshift4 cluster, to reduce external registry components dependency. But the Edge use case, with UPI installation mode, especially disconnected compact cluster, the number of server is limited under such business senario, reduce the server requirement of the external registry server is critical for business success.

4. List any affected packages or components.
external ocp release manifest image registry is replaced by interal image registry.