Merge pull request #527 from k82cn/automated-cherry-pick-of-#517-release-0.3

Automated cherry pick of #517: Updated version to 0.3

Author: k8s-ci-robot

deployment/kube-batch/values.yaml

@@ -4,7 +4,7 @@
 replicaCount: 1
 image:
   repository: kubesigs
-  tag: v0.2
+  tag: v0.3
   pullPolicy: IfNotPresent
 resources:
   limits:

doc/usage/tutorial.md

@@ -11,10 +11,10 @@ To run `kube-batch`, a Kubernetes cluster must start up. Here is a document on [
 
 ### (1) kube-batch image
 
-An official kube-batch image is provided and you can download it from [DockerHub](https://hub.docker.com/r/kubesigs/kube-batch/). The version is `v0.2` now.
+An official kube-batch image is provided and you can download it from [DockerHub](https://hub.docker.com/r/kubesigs/kube-batch/). The version is `v0.3` now.
 
 ```bash
-# docker pull kubesigs/kube-batch:v0.2
+# docker pull kubesigs/kube-batch:v0.3
 ```
 
 ### (2) Create a Kubernetes Deployment for kube-batch
@@ -40,7 +40,7 @@ Verify the release
 ```bash
 # helm list
 NAME        	REVISION	UPDATED                 	STATUS  	CHART                	NAMESPACE
-dozing-otter	1       	Thu Jun 14 18:52:15 2018	DEPLOYED	kube-batch-0.2.0    	kube-system
+dozing-otter	1       	Thu Jun 14 18:52:15 2018	DEPLOYED	kube-batch-0.3.0    	kube-system
 ```
 
 NOTE: `kube-batch` need to collect cluster information(such as Pod, Node, CRD, etc) for scheduling, so the service account used by the deployment must have permission to access those cluster resources, otherwise, `kube-batch` will fail to startup. For users who are not familiar with Kubernetes RBAC, please copy the example/role.yaml into `$GOPATH/src/github.com/kubernetes-sigs/kube-batch/deployment/kube-batch/templates/` and reinstall batch.