Deploying large CRD addons after Starlark conversion fails

cruise-automation / isopod

An expressive DSL and framework for Kubernetes configuration without YAML

Apache License 2.0

482 stars 32 forks source link

Deploying large CRD addons after Starlark conversion fails #65

Closed nitishkrishna closed 4 years ago

nitishkrishna commented 4 years ago

Error seen with strimzi CRDs:

E0713 10:47:57.945154   35592 main.go:243] addons run failed: `install' execution failed: failed addon installation: <addon: kafka-operator-crd> run failed: failed to store run state for `kafka-operator-crd' addon: ConfigMap "kafka-operator-crd-run-bs69sinjlrlom279ccm0" is invalid: []: Too long: must have at most 1048576 characters

jonnylangefeld commented 4 years ago

Adding some details here:

etcd has max size of 1MB
every isopod run stores the current addon.ipd file as configmap for auditing. If an addon is larger than the max of 1MB, the rollout is still successful and live, but it couldn't be stored as configmap
The error is reproducible with the following addon: isopod generate <(curl -s https://strimzi.io/install/latest?namespace=kafka)