bump dashboard image v2.0.0

[govargo]

What type of PR is this?

/kind feature
/area addons

What this PR does / why we need it:

This PR bump up the dashboard addon image to v2.0.0.
I know it's needed to upload preload tarball to GCS.
But I don't have permission to upload it.
Can anyone who can upload support?

Which issue(s) this PR fixes:

Fixes #7847

Does this PR introduce a user-facing change?

Yes. This PR change dashboard's image.
Before: kubernetesui/dashboard:v2.0.0-rc6
After: kubernetesui/dashboard:v2.0.0

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

[k8s-ci-robot]

Hi @govargo. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: govargo
To complete the pull request process, please assign priyawadhwa
You can assign the PR to them by writing /assign @priyawadhwa in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[govargo]

/assign @priyawadhwa

[minikube-bot]

Can one of the admins verify this patch?

[TravisBuddy]

Travis tests have failed

Hey @govargo,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: e116e2c0-84b2-11ea-aa8b-a3fb45836a64

[govargo]

/retest

[k8s-ci-robot]

@govargo: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[govargo]

Unit test fail...but I think this is not directly related to.
I hope retest this

panic: Fail in goroutine after TestCreateSSHShell has completed
goroutine 242 [running]:
testing.(*common).Fail(0xc0008f5e00)
	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/testing/testing.go:609 +0x151
testing.(*common).Errorf(0xc0008f5e00, 0x13574e3, 0x16, 0xc00042bf00, 0x1, 0x1)
	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/testing/testing.go:704 +0x90
k8s.io/minikube/pkg/minikube/tests.(*SSHServer).handleRequest(0xc0000c5680, 0x165a780, 0xc000176d80, 0xc0002eefc0)
	/home/travis/gopath/src/github.com/kubernetes/minikube/pkg/minikube/tests/ssh_mock.go:154 +0x573
k8s.io/minikube/pkg/minikube/tests.(*SSHServer).handleIncomingConnection(0xc0000c5680, 0x165f6a0, 0xc000010268)
	/home/travis/gopath/src/github.com/kubernetes/minikube/pkg/minikube/tests/ssh_mock.go:118 +0x15f
created by k8s.io/minikube/pkg/minikube/tests.(*SSHServer).serve
	/home/travis/gopath/src/github.com/kubernetes/minikube/pkg/minikube/tests/ssh_mock.go:92 +0x4a
FAIL	k8s.io/minikube/pkg/minikube/machine	3.266s

[priyawadhwa]

/ok-to-test

[priyawadhwa]

Hey @govargo that unit test is flaky -- otherwise everything looks good!

[minikube-pr-bot]

kvm2 Driver
docker Driver

[medyagh]

@priyawadhwa this is a good example of the issue this PR was trying to investigate
#7804

right now with this PR, I think with our generated preload tarball, it will invoke a reset and re-pull because the dasbboard is not same verison
we could refactor our preload, DockerImagesPreloaded from Bool to a []string
that would return list of images that need to be pulled again. what do u think ?

[govargo]

I rebased latest master. The flake test doesn't appear this time(unit test success).

[codecov-io]

Codecov Report

Merging #7849 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #7849   +/-   ##
=======================================
  Coverage   35.60%   35.60%           
=======================================
  Files         148      148           
  Lines        9305     9305           
=======================================
  Hits         3313     3313           
  Misses       5595     5595           
  Partials      397      397           

Impacted Files	Coverage Δ
pkg/minikube/download/preload.go	0.00% <ø> (ø)
pkg/minikube/bootstrapper/images/images.go	87.50% <100.00%> (ø)