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.7/hauwei.
- Loading branch information
1 parent
0f79c17
commit 36f082e
Showing
5 changed files
with
7,903 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,6 @@ | ||
vendor: Huawei | ||
name: Huawei Cloud Container Engine | ||
version: v1.7 | ||
website_url: http://www.huaweicloud.com/product/cce.html | ||
documentation_url: http://support.huaweicloud.com/cce/index.html | ||
product_logo_url: http://www.huawei.com/Assets/CBG/img/logo.png |
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,60 @@ | ||
## To reproduce: | ||
|
||
After setting up a cluster on Huawei Cloud, we start `E2E Conformance Tests` on one cluster node with following step: | ||
|
||
### Do Some Env Setting Before Tests | ||
|
||
Because interface `kubectl` under `/home/linux` directory, we export it to `PATH`. | ||
|
||
```shell | ||
cd /home/linux | ||
export PATH=$PATH:$(pwd) | ||
``` | ||
|
||
then, you can use `kubectl` anywhere. | ||
|
||
### Launch E2E Conformance Tests | ||
|
||
1. Launch e2e pod and sonobuoy master under namespace `sonobuoy`. | ||
|
||
```shell | ||
curl -L https://raw.githubusercontent.com/cncf/k8s-conformance/master/sonobuoy-conformance-1.7.yaml | kubectl apply -f - | ||
``` | ||
|
||
2. Check logs of `sonobuoy` pod to see when test can be finished. | ||
|
||
```shell | ||
kubectl logs -f -n sonobuoy sonobuoy | ||
``` | ||
|
||
waitting for line `no-exit was specified, sonobuoy is now blocking` now. | ||
|
||
3. Use `kubectl cp` to bring the results to local machine. | ||
|
||
```shell | ||
kubectl cp sonobuoy/sonobuoy:/tmp/sonobuoy /home/result | ||
``` | ||
|
||
4. Delete the conformance test resources. | ||
|
||
```shell | ||
curl -L https://raw.githubusercontent.com/cncf/k8s-conformance/master/sonobuoy-conformance-1.7.yaml | kubectl delete -f - | ||
``` | ||
|
||
5. Untar the tarball, then add plugins/e2e/results/{e2e.log,junit_01.xml}. | ||
|
||
```shell | ||
cd /home/result | ||
tar -xzf *_sonobuoy_*.tar.gz | ||
``` | ||
|
||
Now, you get e2e result logs and others relative output files. | ||
|
||
### Results Explain | ||
|
||
For some specially reason, you can also get one failure in logs, but just one: | ||
|
||
`[Fail] [k8s.io] Networking [BeforeEach] should provide Internet connection for containers [Conformance]` | ||
|
||
The failed reason can refer to [here](https://github.com/cncf/k8s-conformance/issues/27). | ||
|
Oops, something went wrong.