-
Notifications
You must be signed in to change notification settings - Fork 936
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.18/ridge (#1298)
* Conformance results for v1.17/ridge readme fix * Conformance results for v1.17/ridge * ridge v.18 conformace * add RKS cluster provisioning instructions to readme * fix
- Loading branch information
Showing
4 changed files
with
26,408 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: Ridge | ||
name: Ridge Kubernetes Service | ||
version: v1.0 | ||
website_url: https://ridge.co/ | ||
documentation_url: https://docs.ridge.co | ||
product_logo_url: https://drive.google.com/file/d/19cQeD6QwMz4c7_leqwlX6sJ-JeAzN5ps/view | ||
type: hosted | ||
description: Ridge Kubernetes Service (RKS). RKS is a full k8s managed service that makes it possible to run Kubernetes across Ridge’s edge locations. |
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,56 @@ | ||
# Conformance testing Ridge Kubernetes Service | ||
|
||
### Create RKS cluster | ||
|
||
To create a cluster: | ||
|
||
``` | ||
POST https://api.ridge.co/rks/v1alpha/orgs/{org}/projects/{project}/clusters | ||
``` | ||
`org` is the identifier of your organization | ||
|
||
`project` is the project where you want to create the cluster. | ||
|
||
Place your API key in the header as the token in `Authorization: Bearer` <Token> | ||
|
||
Create a cluster by submitting the following JSON | ||
``` | ||
{ | ||
"node_pools": [ | ||
{ | ||
"name": "my-pool", | ||
"display_name": "My Pool", | ||
"desired_node_count": 2, | ||
"quantities": {"cpu_cores":2,"ram":2147483648,"ephemeral_storage":2147483648} | ||
} | ||
], | ||
"initial_max_cost" :"Unlimited", | ||
"name": "my-cluster", | ||
"display_name": "my-cluster", | ||
"desired_locations": [ | ||
"US--New York" | ||
], | ||
"highly_available": true | ||
} | ||
``` | ||
|
||
for more details and api referance refer to https://docs.ridge.co/reference/getting-started-1 | ||
|
||
### Run conformance tests | ||
|
||
Once the RKS cluster has been provisioned, connect to the cluster and commence the conformance test by following these steps: | ||
|
||
``` | ||
$ go get -u -v github.com/vmware-tanzu/sonobuoy | ||
$ sonobuoy run | ||
$ sonobuoy status | ||
$ sonobuoy logs | ||
$ sonobuoy retrieve ./results | ||
# untar the tarball, then add plugins/e2e/results/global/{e2e.log,junit_01.xml} | ||
``` | ||
|
Oops, something went wrong.