I attempted to deploy AAF using the chart from the OOM master branch.
The helm deploy operation appeared to be successful, but the Helm
release for AAF did not appear in a helm list --all. The tiller logs show:
storage] 2020/08/20 14:05:55 creating release "dev-aaf.v1"
[storage/driver] 2020/08/20 14:05:56 create: failed to create: ConfigMap
"dev-aaf.v1" is invalid: []: Too long: must have at most 1048576 bytes
[tiller] 2020/08/20 14:05:56 warning: Failed to record release dev-aaf:
ConfigMap "dev-aaf.v1" is invalid: []: Too long: must have at most
1048576 bytes
Has anyone else seen this problem? Is there a workaround?
--- Jack Lucas
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21950): https://lists.onap.org/g/onap-discuss/message/21950
Mute This Topic: https://lists.onap.org/mt/76326777/21656
Mute #oom: https://lists.onap.org/g/onap+onap-discuss/mutehashtag/oom
Mute #aaf: https://lists.onap.org/g/onap+onap-discuss/mutehashtag/aaf
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
