Skip to content

Commit

Permalink
add faq info about bundle size (#5559)
Browse files Browse the repository at this point in the history
* add faq info about budle size

* Update website/content/en/docs/faqs/_index.md
  • Loading branch information
camilamacedo86 authored Feb 23, 2022
1 parent bf5f3b7 commit 8c13028
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions website/content/en/docs/faqs/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,3 +230,11 @@ bundle: manifests kustomize ## Generate bundle manifests and metadata, then vali

Note:
Though this is a bug with controller-gen which is used by Operator SDK to generate CRD, this is a workaround from our end to enable users to preserve the field after controller-gen has run.

## What is the bundle limit size? Was this amount increased?

Bundles have a size limitation because their manifests are used to create a configMap, and the Kubernetes API does not
allow configMaps larger than `~1MB`. However, from [OLM](https://github.com/operator-framework/operator-lifecycle-manager) version `v0.19.0` and [OPM](https://github.com/operator-framework/operator-registry) `1.17.5`, these values were increased to `~4MB` because we are compressing them. ([More info](https://github.com/operator-framework/operator-registry/pull/685)).

The change to allow bigger bundles from [OLM](https://github.com/operator-framework/operator-lifecycle-manager) version `v0.19.0` only impacts the full bundle size amount.
Any single manifest within the bundle such as the CRD will still make the bundle uninstallable if it exceeds the default file size limit on clusters (`~1MB`).

0 comments on commit 8c13028

Please sign in to comment.