If anyone else is having issues with helm upgrades as of version 2.15, I'd like to leave my notes on the matter.
Helm as of version 2.15, when you use the
--wait argument, will now wait for the Ingress object to be ready. src: https://github.com/helm/helm/releases/tag/v2.15.0
--waitnow waits for ingress hosts to become ready
Traefik previous to version 1.7 apparently didn't support updating the ingress status, resulting in an empty ingress status, thus, failing your helm upgrade if it contained an ingress object. Tiller just complains that the ingress is not ready (as this is now checked by helm: https://github.com/helm/helm/commit/1d95d8396bd57d26ce98a001526b495c0bb413a5#diff-d18c4d83690679deed0c84f55bf476bdR283)
In traefik 1.7, you should add the publishedService to your traefik configuration so it may be able to update the ingress object and effectively set it's status to ready, so helm doesn't fail.
[kubernetes] [kubernetes.ingressEndpoint] publishedService = "traefik/traefik"
traefik/traefik in publishedService is
<namespace>/<traefik service name>
This would be in your configMap in kubernetes or values.yaml file:
kubernetes: ingressEndpoint: publishedService: "traefik/traefik"