Sandor Szücs

@prageethw this looks for me like a Kubernetes vs client-go version issue. Can you check if a cluster with version `>= 1.17` works?

More information how the object looks like you can find at https://opensource.zalando.com/skipper/kubernetes/routegroup-crd/#routegroup-top-level-object `status:`is very similar to ingress, but the `Ingress` was replaced by `RouteGroup`: ``` status: loadBalancer: routegroup: - hostname:...

https://github.com/hjacobs/kube-resource-report/pull/177 was merged

@elgalu what if the cluster update takes >24h? You defined that we can specify a start time using cron syntax, but there is no "end". Cluster updates can be stuck...

@mikkeloscar maybe you can create an interface for the aws specific handling and use provider packages and let others implement these interfaces. I guess it’s a bit of work. Maybe...

:+1:

@vadeg should be able to merge

@katyanna please change the VERSION file to create the next minor version and explain in the readme.md section what the update to >= the new version will do.

Yeah true I also thought about that and you can change the default in kubernetes-on-aws which we likely already did.

@rverma-nikiai thanks for your request, the helm chart was done by users and reviewed by me at https://github.com/helm/charts/pull/4538#issuecomment-467472040, but since charts only run in GKE and AWS does not care...