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.
Conformance results for v1.14/rke (cncf#624)
- Loading branch information
1 parent
c155bd4
commit 5e7c148
Showing
5 changed files
with
20,540 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,8 @@ | ||
vendor: Rancher Inc. | ||
name: RKE - Rancher Kubernetes Engine | ||
version: v0.2.5-rc1 | ||
website_url: https://github.com/rancher/rke | ||
documentation_url: https://rancher.com/docs/rke/latest/en/ | ||
product_logo_url: https://rancher.com/img/brand-guidelines/assets/logos/png/color/rancher-logo-horiz-color.png | ||
type: Installer | ||
description: Rancher Kubernetes Engine, an extremely simple, lightning fast Kubernetes installer that works everywhere. |
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,62 @@ | ||
# Conformance tests for RKE Kubernetes cluster | ||
|
||
## Node Provisioning | ||
Provision 3 nodes for your cluster. Follow the [OS requirements](https://rancher.com/docs/rke/latest/en/os/) | ||
|
||
## Setup Your `cluster.yml` File | ||
|
||
A minimal 3-node `cluster.yml` file should look like this: | ||
```yaml | ||
kubernetes_version: v1.14.3-rancher1-1 | ||
nodes: | ||
- address: xx.xx.xx.1 | ||
user: root | ||
role: [controlplane,worker,etcd] | ||
- address: xx.xx.xx.2 | ||
user: root | ||
role: [controlplane,worker,etcd] | ||
- address: xx.xx.xx.3 | ||
user: root | ||
role: [controlplane,worker,etcd] | ||
``` | ||
## Run RKE | ||
1. Follow the [installation](https://rancher.com/docs/rke/latest/en/installation/) to install the latest RKE release. | ||
2. In the same directory as your `cluster.yml` file, run: | ||
```bash | ||
$ rke up | ||
``` | ||
3. Wait until the cluster deployment completes successfully. | ||
|
||
## Run Conformance Test | ||
|
||
1. Download a sonobuoy [binary release](https://github.com/heptio/sonobuoy/releases) of the CLI, or build it yourself by running: | ||
```sh | ||
$ go get -u -v github.com/heptio/sonobuoy | ||
``` | ||
|
||
2. Configure your kubeconfig file by running the following command in the same directory as your `cluster.yml` file: | ||
```sh | ||
$ export KUBECONFIG="kube_config_cluster.yml" | ||
``` | ||
|
||
4. Run sonobuoy: | ||
```sh | ||
$ sonobuoy run | ||
``` | ||
|
||
4. Watch the logs: | ||
```sh | ||
$ sonobuoy logs | ||
``` | ||
|
||
5. Check the status: | ||
```sh | ||
$ sonobuoy status | ||
``` | ||
|
||
6. Once the status commands shows the run as completed, you can download the results tar.gz file: | ||
```sh | ||
$ sonobuoy retrieve | ||
``` |
Oops, something went wrong.