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.20/openstack-magnum (cncf#1320)
- Loading branch information
Showing
4 changed files
with
30,437 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: OpenStack Foundation | ||
name: Magnum | ||
version: 11.0.0 | ||
website_url: https://docs.openstack.org/magnum/latest/ | ||
repo_url: https://opendev.org/openstack/magnum/ | ||
documentation_url: https://docs.openstack.org/magnum/latest/user/#kubernetes | ||
type: installer | ||
description: Magnum is an OpenStack API service developed by the OpenStack Containers Team making container orchestration engines such as Kubernetes available as a first class resources in OpenStack. | ||
product_logo_url: https://www.openstack.org/themes/openstack/images/project-mascots/Magnum/OpenStack_Project_Magnum_vertical.eps |
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,55 @@ | ||
# OpenStack Magnum (Kubernetes) Conformance | ||
|
||
## Create Kubernetes Cluster | ||
|
||
Setup an OpenStack environment with devstack at master branch. Then create your personal keypair by command: | ||
|
||
openstack keypair create my-key --public-key ~/.ssh/id_rsa.pub | ||
|
||
Now you can create a Kubernetes cluster template by command: | ||
|
||
openstack coe cluster template create k8s --network-driver calico --flavor ds4G --master-flavor ds4G --coe kubernetes --external-network public --image fedora-coreos-33.20210117.3.2-openstack.x86_64 | ||
|
||
Then you can create a Kubernetes cluster by below command: | ||
|
||
openstack coe cluster create k8s-calico-coreos --cluster-template k8s --labels=kube_tag=v1.20.2-rancher1 --node-count=2 | ||
|
||
After the cluster is created, run the following command to obtain the configuration/certificate files: | ||
|
||
eval $(openstack coe cluster config k8s-calico-coreos) | ||
|
||
## Conformance Test | ||
|
||
Install Sonobuoy: | ||
|
||
VERSION=0.20.0 && \ | ||
curl -L "https://github.com/vmware-tanzu/sonobuoy/releases/download/v${VERSION}/sonobuoy_${VERSION}_linux_amd64.tar.gz" --output sonobuoy.tar.gz && \ | ||
mkdir -p tmp && \ | ||
tar -xzf sonobuoy.tar.gz -C tmp/ && \ | ||
chmod +x tmp/sonobuoy && \ | ||
sudo mv tmp/sonobuoy /usr/local/bin/sonobuoy && \ | ||
rm -rf sonobuoy.tar.gz tmp | ||
|
||
Now run the test: | ||
|
||
sonobuoy run --mode=certified-conformance | ||
|
||
Check status: | ||
|
||
sonobuoy logs | ||
|
||
Follow logs: | ||
|
||
sonobuoy logs -f | grep PASSED | ||
|
||
Retrieve results: | ||
|
||
outfile=$(sonobuoy retrieve); mkdir ./results; tar xzf $outfile -C ./results; cp results/plugins/e2e/results/global/* ./ | ||
|
||
Cleaning up: | ||
|
||
sonobuoy delete --all; rm -rf results/ *.tar.gz | ||
|
||
## Testing | ||
|
||
Once the configuration has been created, then you can follow the conformance suite [instructions](https://github.com/cncf/k8s-conformance/blob/master/instructions.md#running) to run the conformance test. |
Oops, something went wrong.