-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
4.13
-
False
-
None
-
False
-
Not Selected
-
-
Description of problem:
Operator-sdk run bundle failed if the ConfigMap size exceed 1 MiB.
Version-Release number of selected component (if applicable):
operator-sdk version: "v1.28.0-ocp", commit: "d2e54511f9197e06241680d1b1e7739f3fed4aad", kubernetes version: "v1.26.0", go version: "go1.19.6", GOOS: "linux", GOARCH: "amd64"
How reproducible:
always
Steps to Reproduce:
1.operator-sdk run bundle quay.io/olmqe/elasticsearch-operator-bundle:v0.0.1
Actual results:
$operator-sdk run bundle quay.io/olmqe/elasticsearch-operator-bundle:v0.0.1 INFO[0020] Creating a File-Based Catalog of the bundle "quay.io/olmqe/elasticsearch-operator-bundle:v0.0.1" INFO[0026] Generated a valid File-Based Catalog FATA[0030] Failed to run bundle: create catalog: error creating registry pod: error building registry pod definition: configMap error: error updating ConfigMap: error creating ConfigMap: ConfigMap "elasticsearch-operator-catalog-configmap-partition-2" is invalid: []: Too long: must have at most 1048576 bytes
Expected results:
1.run bundle success
Additional info:
The upstream issue link: https://github.com/operator-framework/operator-sdk/issues/6323