-
Notifications
You must be signed in to change notification settings - Fork 934
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Conformance results for v1.31/microk8s (#3556)
Signed-off-by: Claudiu Belu <[email protected]>
- Loading branch information
1 parent
e3bcf9d
commit caa022b
Showing
4 changed files
with
65,524 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
vendor: Canonical Ltd | ||
name: MicroK8s | ||
version: v1.31.3 | ||
website_url: https://microk8s.io | ||
documentation_url: https://microk8s.io/docs/ | ||
product_logo_url: https://assets.ubuntu.com/v1/9309d097-MicroK8s_SnapStore_icon.svg | ||
type: distribution | ||
description: 'A small, fast, single-package Kubernetes for developers, IoT and edge.' | ||
contact_email_address: [email protected] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# Reproducing the test results | ||
|
||
## Deploy MicroK8s | ||
|
||
Follow the instructions at https://microk8s.io to snap install microk8s on two machines. | ||
```sh | ||
$ sudo snap install microk8s --channel 1.31/stable --classic | ||
``` | ||
|
||
Create a cluster by running on the first machine: | ||
```sh | ||
$ sudo microk8s add-node | ||
``` | ||
|
||
Use the connection string on the second machine to form the cluster: | ||
```sh | ||
$ sudo microk8s join 10.227.69.102:25000/d35aea1606887db2ea326ed6de93c321/cb463cb3b0e4 --worker | ||
``` | ||
|
||
## Trigger the tests and get back the results | ||
|
||
We follow the [official instructions](https://github.com/cncf/k8s-conformance/blob/master/instructions.md): | ||
|
||
## Run Conformance Test | ||
|
||
1. Download a [binary release](https://github.com/heptio/sonobuoy/releases) of sonobuoy, or build it yourself by running: | ||
```sh | ||
$ wget https://github.com/vmware-tanzu/sonobuoy/releases/download/v0.57.2/sonobuoy_0.57.2_linux_amd64.tar.gz | ||
$ tar -zxvf ./sonobuoy_0.57.2_linux_amd64.tar.gz | ||
``` | ||
|
||
2. Run sonobuoy: | ||
```sh | ||
$ sudo ./sonobuoy run \ | ||
--mode certified-conformance \ | ||
--kubeconfig /var/snap/microk8s/current/credentials/client.config \ | ||
--plugin-env=e2e.E2E_EXTRA_ARGS="--non-blocking-taints=node-role.kubernetes.io/controller --ginkgo.v" | ||
``` | ||
|
||
3. Check the status: | ||
```sh | ||
$ sudo ./sonobuoy status --kubeconfig /var/snap/microk8s/current/credentials/client.config | ||
``` | ||
|
||
4. Retrieve results and extract | ||
```sh | ||
$ sudo ./sonobuoy retrieve --kubeconfig /var/snap/microk8s/current/credentials/client.config | ||
``` |
Oops, something went wrong.