Upgrade with Helm meet failure seems as configmap limitation exceed

12/25/2018

I was using the helm upgrade -i xxx myfoo to install/upgrade myfoo,

I follow all the standard doc, but this failure ALWAYS happend as soon as I upgrade at the 7th upgration!

When I began to upgrade at the 7th time, it told me below failure:

Error: UPGRADE FAILED: ConfigMap "myfoo.v7" is invalid: []: Too long: must have at most 1048576 characters

This is really frustrating! Why do this happen?

-- user10814765

kubernetes

kubernetes-helm

Similar Questions

create pods staying at ContainerCreating

Error when setting up glusterfs on Kubernetes: volume create: heketidbstorage: failed: Host not connected

Deploying a Computer Vision pipeline using Kubeflow on Kubernetes

Enable access to Kubernetes Dashboard without kubectl proxy

Pod has more resources than expected

Prometheus Server with Dynamic Rules

How to perform custom authentication with kubernetes Ingress

How to use skaffold with volumes

kubctl get deployment READY 0/0 meaning

Writing to kubernetes parameter store from nodejs app

1 Answer

12/26/2018

Thank you for your help, I now understand what's going on.

I added some bigger file in chart/ dir, which cause the helm package size exceed 1M.

after remove these bigger files, it works back to normal. And I know why there is .helmignore file now, it is used to tell helm not include them in final helm package file(*.tgz)

-- user10814765

Source: StackOverflow