You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributor-docs/development/tests/conformance-tests-sonobuoy.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ status: Draft
5
5
track: Global
6
6
---
7
7
8
-
SovereignCloudStack (SCS) makes use of [Sonobuoy][sonobuoy]] as a test framework to run its tests on Kubernetes clusters, which are to be audited for compliance.
8
+
SovereignCloudStack (SCS) makes use of [Sonobuoy][sonobuoy] as a test framework to run its tests on Kubernetes clusters, which are to be audited for compliance.
9
9
The aim of using this framework is to make the execution of tests on a KaaS infrastructure as simple as possible.
10
10
Hence this reduces the effort required to establish SCS conformity to a minimum.
11
11
12
12
In short this is achieved by storing all tests in a container image, which can then be called and launched on the clusters managed by sonoobuoy.
13
13
14
-
> A more detailed description of why the SCS has decided to use sonobuoys can be found on the corresponding [Decsision Record][sonbouy-decision-record]
14
+
> A more detailed description of why the SCS has decided to use sonobuoys can be found on the corresponding [Decsision Record][sonbouy-decision-record].
15
15
> In addition, sonobuoy is also used as the toolset for executing Kubernetes very own [conformance tests][k8s-conformance].
16
16
17
17
@@ -192,28 +192,27 @@ sonobuoy status
192
192
Once all tests have been executed successfully, you can read the results and receive feedback.
193
193
You can call up the results as follows:
194
194
195
-
```
196
-
TODO:!!! be described in more detail
197
-
```
195
+
> TODO:!!! to be described in more detail
196
+
198
197
199
198
200
199
201
200
## Clean up after:
202
201
202
+
To clean up the resourcec used for development, you can use the following commands:
0 commit comments