add faq info about bundle size (#5559)

* add faq info about budle size

* Update website/content/en/docs/faqs/_index.md

Author: camilamacedo86

website/content/en/docs/faqs/_index.md

@@ -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`).