Testing PR Conformance results for v1.20/k0s v0.10.0 cncf#1310

v1.20/k0s/PRODUCT.yaml

@@ -1,9 +1,9 @@
 vendor: Mirantis
 name: k0s
-version: v0.9.0
+version: v0.10.0
 website_url: https://k0sproject.io
 repo_url: https://github.com/k0sproject/k0s
-documentation_url: https://github.com/k0sproject/k0s/tree/main/docs
+documentation_url: https://docs.k0sproject.io/v0.10.0/
 product_logo_url: https://raw.githubusercontent.com/k0sproject/k0s/main/k0s-logo-full-color.svg
 type: Distribution
-description: "k0s is a single binary all-inclusive Kubernetes distribution with all the required bells and whistles preconfigured to make building a Kubernetes clusters a matter of just copying an executable to every host and running it."
+description: "k0s is a single binary all-inclusive Kubernetes distribution with all the required bells and whistles preconfigured to make building a Kubernetes clusters a matter of just copying an executable to every host and running it."

v1.20/k0s/README.md

@@ -6,7 +6,7 @@ Full instructions on how to set up a k0s cluster can be found [here](https://git
 k0s runs either as a single node (server with `--enable-worker`), or as a controller/worker cluster.
 These instructions assume you have one or more linux or arm boxes ready for installation.
 
-Download the k0s v0.9.0 binary from [releases](https://github.com/k0sproject/k0s/releases/v0.9.0) and push it to all the nodes you wish to connect to the cluster.
+Download the k0s v0.10.0 binary from [releases](https://github.com/k0sproject/k0s/releases/v0.10.0) and push it to all the nodes you wish to connect to the cluster.
 
 ## Cluster Setup
 #### Single node
@@ -35,7 +35,7 @@ $ go get -u -v github.com/vmware-tanzu/sonobuoy
 Deploy a Sonobuoy pod to your cluster with:
 ```
 $ export KUBECONFIG=/var/lib/k0s/pki/admin.conf
-$ sonobuoy run --mode=certified-conformance
+$ sonobuoy run --mode=certified-conformance --kube-conformance-image-version=v1.20.2
 ```
 The test will take more than an hour to complete, but you can follow the logs by running:
 ```