release: Prepare v0.10.2 (aquasecurity#573)

Signed-off-by: Daniel Pacak <pacak.daniel@gmail.com>

README.md

@@ -30,7 +30,7 @@ Starboard can be run in two different modes:
   cluster - for example, initiating a vulnerability scan when a new pod is started.
 
 > **NOTE** Even though manual scanning through the command-line is useful, the fact that it's not automated makes it
-> less suitable with a large number of Kubernetes workloads. Therefore, the [operator] provides a better option
+> less suitable with numerous Kubernetes workloads. Therefore, the [operator] provides a better option
 > for these scenarios, constantly monitoring built-in Kubernetes resources, such as Deployments, and running appropriate
 > scanners against the underlying deployment descriptors.
 

deploy/helm/Chart.yaml

@@ -11,7 +11,7 @@ version: 0.5.1
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: 0.10.2-rc1
+appVersion: 0.10.2
 
 # kubeVersion: A SemVer range of compatible Kubernetes versions (optional)
 

deploy/static/06-starboard-operator.deployment.yaml

@@ -23,7 +23,7 @@ spec:
       securityContext: {}
       containers:
         - name: operator
-          image: docker.io/aquasec/starboard-operator:0.10.2-rc1
+          image: docker.io/aquasec/starboard-operator:0.10.2
           imagePullPolicy: IfNotPresent
           securityContext:
             privileged: false

docs/operator/getting-started.md

@@ -72,14 +72,14 @@ default      └─VulnerabilityReport/replicaset-nginx-7ff78f74b9-nginx  -
 Moving forward, let's update the container image of the `nginx` Deployment from `nginx:1.16` to `nginx:1.17`. This will
 trigger a rolling update of the Deployment and eventually create another ReplicaSet.
 
-```console
+```
 kubectl set image deployment nginx nginx=nginx:1.17
 ```
 
 Even this time the operator will pick up changes and rescan our Deployment with updated configuration:
 
 ```console
-kubectl tree deploy nginx
+$ kubectl tree deploy nginx
 NAMESPACE  NAME                                                       READY  REASON  AGE
 default    Deployment/nginx                                           -              6m36s
 default    ├─ReplicaSet/nginx-549f5fcb58                              -              2m47s

mkdocs.yml

@@ -72,10 +72,10 @@ extra:
   version:
     provider: mike
   var:
-    tag: "v0.10.2-rc1"
+    tag: "v0.10.2"
     tag_prev: "v0.10.1"
     build:
-      version: "0.10.2-rc1"
+      version: "0.10.2"
       commit: "21e893cb41c75144f9877735303bbf783c3f80bc"
       date: "2021-04-21T19:48:38Z"
     chart: