When unpacking bundles, we currently push them into config maps in order to maintain their state on the cluster. Config maps have a hard limit of 1mb, so for very large bundles they require more space than what a config map can apply. We need to investigate possible solutions (sharding?) in order to support large bundles.

Acceptance Criteria:

• Unpack bundles larger than 1mb so that they can be installed on a cluster by OLM.
• large bundles are reasonably reduced in size without operator author intervention
• OLM implementation to store bundle content in a ConfigMap should not be impacted
• the supported size is not unlimited, we should have some sort guidance for users
• we potentially need to backport this to older OLM versions / OCP releases

This epic is now tracking the stop gap solution provided here: https://github.com/operator-framework/operator-registry/pull/685

The original epic to track unpacking bundles of arbitrary lengths was cloned here: https://issues.redhat.com/browse/OLM-2236

Background:

• this is a stop gap, the final solution is going to be the bundle API (OLM-2150)