prageethw

@mikkeloscar yes default role exist in `kube-system` namespace, it seems the issue is with `custom-metrics-resource-reader `and `custom-metrics-resource-collector `that gets created in the namespace I install the adopter it seems.

@mikkeloscar Thanks for the reply, yeah installing in `kube-system `is always an option though not sure whether that will be the best practice, generally, I like to keep `Kube-system` untouched,...

@mikkeloscar fair point, I think TBH that is an extreme measure if someone can access to `custom-metrics-resource-collector` and `custom-metrics-resource-reader`, most likely he is already inside the cluster.

@szuecs tried with k8s 1.17.X still fails ``` known (get configmaps) kube-metrics-adapter-7b79498f9-g42j8 kube-metrics-adapter E0717 09:33:22.393669 1 reflector.go:307] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:105: Failed to watch *v1.ConfigMap: unknown (get configmaps) kube-metrics-adapter-7b79498f9-g42j8 kube-metrics-adapter E0717 09:33:22.394841 1...

@mikkeloscar I had a look in the helm chart(banzai), it seems it already exists, but still, I see the error in the logs, but It seems the metrics are pulled...

@mikkeloscar yeah you are right it was not in collector ClusterRole though. I just added it and sent a pull to helm.

fix https://github.com/zalando-incubator/kube-metrics-adapter/pull/181 will fix this issue once it is merged.

@gjcarneiro I think that's the benefit of this chaos solution giving total control to the victim whether he should be treated as a victim or not. there are other chaos...