Update version to 2.0.0-rc1 (#4746)

README.md

@@ -17,7 +17,7 @@ Kubernetes Dashboard is a general purpose, web-based UI for Kubernetes clusters.
 To deploy Dashboard, execute following command:
 
 ```sh
-$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml
+$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc1/aio/deploy/recommended.yaml
 ```
 
 To access Dashboard from your local workstation you must create a secure channel to your Kubernetes cluster. Run the following command:
@@ -34,7 +34,7 @@ http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kube
 To find out how to create sample user and log in follow [Creating sample user](docs/user/access-control/creating-sample-user.md) guide.
 
 **NOTE:**
-* Kubeconfig Authentication method does not support external identity providers or certificate-based authentication. 
+* Kubeconfig Authentication method does not support external identity providers or certificate-based authentication.
 * Dashboard can only be accessed over HTTPS
 * [Heapster](https://github.com/kubernetes/heapster/) has to be running in the cluster for the metrics and graphs to be available. Read more about it in [Integrations](docs/user/integrations.md) guide.
 

aio/deploy/alternative.yaml

@@ -176,7 +176,7 @@ spec:
     spec:
       containers:
         - name: kubernetes-dashboard
-          image: kubernetesui/dashboard:v2.0.0-beta8
+          image: kubernetesui/dashboard:v2.0.0-rc1
           ports:
             - containerPort: 9090
               protocol: TCP

aio/deploy/alternative/06_dashboard-deployment.yaml

@@ -34,7 +34,7 @@ spec:
     spec:
       containers:
         - name: kubernetes-dashboard
-          image: kubernetesui/dashboard:v2.0.0-beta8
+          image: kubernetesui/dashboard:v2.0.0-rc1
           ports:
             - containerPort: 9090
               protocol: TCP

aio/deploy/recommended.yaml

@@ -187,7 +187,7 @@ spec:
     spec:
       containers:
         - name: kubernetes-dashboard
-          image: kubernetesui/dashboard:v2.0.0-beta8
+          image: kubernetesui/dashboard:v2.0.0-rc1
           imagePullPolicy: Always
           ports:
             - containerPort: 8443

aio/deploy/recommended/06_dashboard-deployment.yaml

@@ -34,7 +34,7 @@ spec:
     spec:
       containers:
         - name: kubernetes-dashboard
-          image: kubernetesui/dashboard:v2.0.0-beta8
+          image: kubernetesui/dashboard:v2.0.0-rc1
           imagePullPolicy: Always
           ports:
             - containerPort: 8443

aio/gulp/conf.js

@@ -53,7 +53,7 @@ const version = {
   /**
    * Current release version of the project.
    */
-  release: 'v2.0.0-beta8',
+  release: 'v2.0.0-rc1',
   /**
    * Version name of the head release of the project.
    */

docs/user/installation.md

@@ -10,7 +10,7 @@ The fastest way of deploying Dashboard has been described in our [README](../../
 
 ### Recommended setup
 
-To access Dashboard directly (without `kubectl proxy`) valid certificates should be used to establish a secure HTTPS connection. They can be generated using public trusted Certificate Authorities like [Let's Encrypt](https://letsencrypt.org/), optionally [Cert-Manager](https://docs.cert-manager.io) can auto-issue and auto-renew them. Use them to replace the auto-generated certificates from Dashboard. 
+To access Dashboard directly (without `kubectl proxy`) valid certificates should be used to establish a secure HTTPS connection. They can be generated using public trusted Certificate Authorities like [Let's Encrypt](https://letsencrypt.org/), optionally [Cert-Manager](https://docs.cert-manager.io) can auto-issue and auto-renew them. Use them to replace the auto-generated certificates from Dashboard.
 
 By default self-signed certificates are generated and stored in-memory. In case you would like to use your custom certificates follow the below steps, otherwise skip directly to the Dashboard deploy part.
 
@@ -23,10 +23,10 @@ kubectl create secret generic kubernetes-dashboard-certs --from-file=$HOME/certs
 For Dashboard to pickup the certificates, you must pass arguments `--tls-cert-file=/tls.crt` and `--tls-key-file=/tls.key` to the container. You can edit YAML definition and deploy Dashboard in one go:
 
 ```
-kubectl create --edit -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml
+kubectl create --edit -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc1/aio/deploy/recommended.yaml
 ```
- 
-Under Deployment section, add arguments to pod definition, it should look as follows:  
+
+Under Deployment section, add arguments to pod definition, it should look as follows:
 ```
       containers:
       - args:
@@ -42,7 +42,7 @@ This setup is not fully secure. Certificates are not used and Dashboard is expos
 To deploy Dashboard execute following command:
 
 ```
-kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/alternative.yaml
+kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc1/aio/deploy/alternative.yaml
 ```
 
 
@@ -55,7 +55,7 @@ Besides official releases, there are also development releases, that are pushed
 In most of the use cases you need to execute the following command to deploy latest development release:
 
 ```
-$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/head.yaml
+$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc1/aio/deploy/head.yaml
 ```
 
 ### Update

package.json

@@ -1,6 +1,6 @@
 {
   "name": "kubernetes-dashboard",
-  "version": "2.0.0-beta8",
+  "version": "2.0.0-rc1",
   "repository": {
     "type": "git",
     "url": "https://github.com/kubernetes/dashboard.git"