forked from cncf/k8s-conformance
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Nutanix Karbon CNCF conformance results submission for 1.16 (cncf#990)
- Loading branch information
1 parent
467e821
commit 135e2bc
Showing
5 changed files
with
27,361 additions
and
94 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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: Nutanix | ||
name: Karbon | ||
version: v2.0.1 | ||
documentation_url: https://portal.nutanix.com/page/documents/details/?targetId=Release-Notes-Karbon-v2_0_1%3ARelease-Notes-Karbon-v2_0_1 | ||
website_url: https://www.nutanix.com | ||
product_logo_url: https://www.nutanix.com/wp-content/uploads/2017/11/nutanix.png | ||
type: hosted | ||
description: Managed Kubernetes offering by Nutanix |
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,42 @@ | ||
Nutanix Karbon | ||
=== | ||
To Reproduce | ||
--- | ||
On Nutanix Prism Central, enable Karbon (managed Kubernetes offering of Nutanix) by following | ||
the instructions mentioned below: | ||
1. Log on to Prism Central. | ||
2. Click the menu icon. | ||
3. In the Services option, click Karbon. | ||
4. `Karbon is successfully enabled` message will indicate that Karbon has been enabled successfully. | ||
5. In the Karbon Console, a message directs you to download a node OS image. | ||
6. Once image downlao is successfully, use the UI cluster create wizard | ||
to fill up all the necessary information: | ||
a) Name of cluster | ||
b) Network to be used. | ||
c) Choose development cluster or production cluster. | ||
d) Choose the K8s version to be deployed to 1.16.* | ||
e) Select the storage container. | ||
f) Initiate cluster creation. | ||
g) UI will display the status of deployment. | ||
|
||
Next, follow the steps to install a fresh cluster, choosing `v1.16` as the Kubernetes | ||
version and `centos` as the base image. | ||
|
||
Once the cluster is deployed, you can download the kubeconfig to your local machine using | ||
the steps described: | ||
1. In the Clusters view, select a cluster from the list by checking the adjacent box. | ||
2. Click the Actions drop-down. | ||
3. Click Download Kubeconfig | ||
4. Under Instructions, click Download. | ||
5. Once the file is downloaded(example: prod1-kubectl.cfg), run the following command: | ||
`export KUBECONFIG=/path/to/prod1-kubectl.cfg` | ||
6. Run the following command to test the cluster: | ||
`kubectl cluster-info` | ||
|
||
Then, build Sonobuoy(the standard tool for running these tests) by running `go get -u -v github.com/heptio/sonobuoy`. | ||
This would build the latest Sonobuoy release [v0.17.2](https://github.com/heptio/sonobuoy/releases/tag/v0.17.2). | ||
|
||
Deploy a Sonobuoy pod to the deployed cluster using `sonobuoy run`, which will initiate the tests to run on | ||
the cluster. Use `sonobuoy status` to track the status of the test run. Once it completes, you | ||
can inspect the logs using `sonobuoy logs` and/or retrieve it using `sonobuoy retrieve` | ||
to copy from the main Sonobuoy pod to a local directory. |
Oops, something went wrong.