Skip to content

Commit

Permalink
update daocloud (#992)
Browse files Browse the repository at this point in the history
Co-authored-by: panpan0000 <peter.pan@daocloud.io>
  • Loading branch information
zhouya0 and panpan0000 authored Jun 10, 2020
1 parent 346f30a commit aa7cbb3
Show file tree
Hide file tree
Showing 4 changed files with 28,630 additions and 0 deletions.
6 changes: 6 additions & 0 deletions v1.18/daocloud/PRODUCT.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
vendor: DaoCloud
name: DaoCloud Enterprise
version: v4.0.1-32741
website_url: https://www.daocloud.io/dce
documentation_url: https://download.daocloud.io/DaoCloud_Enterprise/DaoCloud_Enterprise/4.0.1
product_logo_url: https://guide.daocloud.io/download/attachments/524290/global.logo?version=2&modificationDate=1469173304363&api=v2
27 changes: 27 additions & 0 deletions v1.18/daocloud/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
DaoCloud Enterprise

DaoCloud Enterprise is a platform based on Kubernetes which developed by [DaoCloud](https://www.daocloud.io).

## How to Reproduce

First install DaoCloud Enterprise 4.0.1, which is based on Kubernetes 1.18.0. To install DaoCloud Enterprise, run the following commands on CentOS 7.7 System:
```
sudo su
curl -L https://dce.daocloud.io/DaoCloud_Enterprise/4.0.1os-requirements > ./os-requirements
chmod +x ./os-requirements
./os-requirements
bash -c "$(docker run -i --rm daocloud.io/daocloud/dce:4.0.1-32741 install)"
```
To add more nodes to the cluster, the user need log into DaoCloud Enterprise control panel and follow instructions under node management section.

After the installation, run ```docker exec -it `docker ps | grep dce-kube-controller | awk '{print$1}'` bash``` to enter the DaoCloud Enterprise Kubernetes controller container.

The standard tool for running these tests is
[Sonobuoy](https://github.com/heptio/sonobuoy), and the standard way to run
these in your cluster is with `curl -L https://github.com/raw/cncf/k8s-conformance/master/sonobuoy-conformance.yaml | kubectl apply -f -`.

Watch Sonobuoy's logs with `kubectl logs -f -n sonobuoy sonobuoy` and wait for
the line `no-exit was specified, sonobuoy is now blocking`. At this point, use
`kubectl cp` to bring the results to your local machine, expand the tarball, and
retain the 3 files `plugins/e2e/results/{e2e.log,junit.xml,version.txt}`, which will
be included in your submission.
Loading

0 comments on commit aa7cbb3

Please sign in to comment.