forked from cncf/k8s-conformance
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add conformance results for v1.14/kubermatic (cncf#612)
- Loading branch information
1 parent
af49ac8
commit 8319bd2
Showing
4 changed files
with
21,362 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,7 @@ | ||
vendor: Loodse | ||
name: Kubermatic Container Engine | ||
version: v2.10 | ||
website_url: https://loodse.com | ||
documentation_url: https://docs.kubermatic.io/ | ||
type: Distribution | ||
product_logo_url: https://drive.google.com/file/d/1NdEwTa_Aco_urdyY7bhDjJEPcpyAYRY9 |
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,52 @@ | ||
# To reproduce | ||
|
||
## Set up the cluster | ||
|
||
1. Login to https://cloud.kubermatic.io/ | ||
2. Press the "Create Cluster" button | ||
3. Pick Kubernetes version v1.14.x | ||
4. Complete the create cluster wizard with AWS. | ||
|
||
When the cluster is up and running, | ||
|
||
1. Download the kubeconfig file. | ||
2. Set the KUBECONFIG environment variable `export KUBECONFIG=$PWD/kubeconfig`. | ||
|
||
## Run the conformance test | ||
|
||
Download a [binary release](https://github.com/heptio/sonobuoy/releases) of the CLI, or build it yourself by running: | ||
|
||
``` | ||
$ go get -u -v github.com/heptio/sonobuoy | ||
``` | ||
|
||
Deploy a Sonobuoy pod to your cluster with: | ||
|
||
``` | ||
$ sonobuoy run | ||
``` | ||
|
||
View actively running pods: | ||
|
||
``` | ||
$ sonobuoy status | ||
``` | ||
|
||
To inspect the logs: | ||
|
||
``` | ||
$ sonobuoy logs | ||
``` | ||
|
||
Once `sonobuoy status` shows the run as `completed`, copy the output directory from the main Sonobuoy pod to a local directory: | ||
|
||
``` | ||
$ outfile=$(sonobuoy retrieve) | ||
``` | ||
|
||
This copies a single `.tar.gz` snapshot from the Sonobuoy pod into your local | ||
`.` directory. Extract the contents into `./results` with: | ||
|
||
``` | ||
mkdir ./results; tar xzf $outfile -C ./results | ||
``` |
Oops, something went wrong.