Kube-prometheus: Use kube-state-metrics jsonnet dependency

[lilic]

As kube-state-metrics now has switched to including jsonnet we should remove ours in favour of that and bring it in as a dependency. Same goes for the alerts.

See https://github.com/coreos/kube-prometheus/pull/368#issuecomment-572694051

[olegmayko]

I can submit PR after holidays (beginning of Feb). would it be okay?

[brancz]

If no one will have done it by then, please! :)

[lilic]

Yes go for it! Thanks!

[olegmayko]

Hi, I had a quick look into the ksm lib on kube-prometheus, it contains additionally ksm autoscaler. Thus, there are 2 possibilities:

• remove autoscaler and generate sts (which has autosharding) which can replace ksm autoscaler in some way;
• keep autoscaler and just use standard deployment from kube-state-metrics repo.
  what do you think?
  //cc @brancz
  //cc @LiliC

[brancz]

I think we should default to the standard deployment. We can figure out afterwards how people might be able to opt into the autosharding feature with the statefulset.

[lilic]

I would like to end up with the similar deployment we already have in this repo just that it uses the upstream jsonnet. In a follow up issue we should look at how to easily opt into the new autosharding feature. Main point of this issue is to remove the ned to manually update the ksm deployments.

[lilic]

I think this can be closed now. If we need to do follow up we can open a new issue.