I've been attempting to deploy AAF (from the OOM master branch charts), but the Helm release (in my case testdev123-aaf) is not being recorded because the release configMap is too large. The tiller logs show: [storage] 2020/08/20 13:42:32 creating release "testdev123-aaf.v1" [storage/driver] 2020/08/20 13:42:33 create: failed to create: ConfigMap "testdev123-aaf.v1" is invalid: []: Too long: must have at most 1048576 bytes [tiller] 2020/08/20 13:42:33 warning: Failed to record release testdev123-aaf: ConfigMap "testdev123-aaf.v1" is invalid: []: Too long: must have at most 1048576 bytes
Has anyone else seen this? Is there any fix or workaround? (I tried using a shorter name for the release ["dev" instead of "testdev123"], but that didn't trim enough bytes from the configMap to make a difference.) (The k8s resources for AAF are still being created, but AAF doesn't come up because of some failed readiness checks.) --- Jack Lucas -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21949): https://lists.onap.org/g/onap-discuss/message/21949 Mute This Topic: https://lists.onap.org/mt/76326776/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
