Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-2236

Support unpacking bundles of arbitrary lengths (greater than 1mb)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • Support unpacking bundles of arbitrary lengths (greater than 1mb)
    • True
    • This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic.
    • False
    • Impediment
    • Undefined
    • M

      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

      Background:

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

       

          There are no Sub-Tasks for this issue.

              Unassigned Unassigned
              davegord@redhat.com Dave Gordon
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: