"kube-dns" benchmark jobs are actually testing CoreDNS, not kube-dns

[danwinship]

The pull-perf-tests-benchmark-kube-dns and ci-benchmark-kube-dns-master jobs have names suggesting that they test the old kube-dns, but both actually run in clusters with CoreDNS. (In contrast, the SIG Network tests with "kube-dns" in their names actually do test kube-dns specifically, in contrast to the more-standard CoreDNS tests.)

Maybe just remove the kube- from the names? (I would have submitted a PR but I don't want to break dashboards, etc...)

(It seems that these jobs have always tested CoreDNS: the periodic job was created in #10366, a month after CoreDNS became the default for GCE CI clusters in kubernetes/kubernetes#69883.)

(Noticed as part of kubernetes/kubernetes#137556.)

/sig scalability
@kubernetes/sig-scalability

[aojea]

I do no think there are active mainteinrs for those jobs

• https://testgrid.k8s.io/sig-scalability-benchmarks#kube-dns
• https://testgrid.k8s.io/sig-scalability-benchmarks#node-local-dns

[danwinship]

meaning what? nobody cares and we should just delete them?

[aojea]

meaning what? nobody cares and we should just delete them?

I can not say, some teams internally fork this repo and keep running the test, so if we change anything that people will break most probably , a change on the name changes the dashboards ... if nobody uses them then we just run less tests