This repository was archived by the owner on Oct 14, 2020. It is now read-only.
File tree Expand file tree Collapse file tree 1 file changed +9
-3
lines changed
Expand file tree Collapse file tree 1 file changed +9
-3
lines changed Original file line number Diff line number Diff line change 1616
1717<!-- toc -->
1818
19+ - [ Overview] ( #overview )
1920- [ Purpose of this Project] ( #purpose-of-this-project )
2021- [ Quickstart] ( #quickstart )
21- - [ How Does it Work?] ( #how-does-it-work )
22+ - [ Prerequisites] ( #prerequisites )
23+ - [ Deployment] ( #deployment )
24+ - [ How does it work?] ( #how-does-it-work )
2225- [ Architecture] ( #architecture )
23- - [ Roadmap] ( #roadmap )
26+ - [ License] ( #license )
27+ - [ Community] ( #community )
28+ - [ Contributing] ( #contributing )
29+ - [ Author Information] ( #author-information )
2430
2531For additional documentation aspects please have a look at our:
2632
@@ -72,7 +78,7 @@ helm install zap ./integrations/zap/
7278# Now everything is installed. You can try deploying scans from the `operator/config/samples/` directory
7379
7480# E.g. www.securecodebox.io sslyze scan
75- kubectl apply apply -f operator/config/samples/execution_v1_scan/sslyze_securecodebox_io.yaml
81+ kubectl apply -f operator/config/samples/execution_v1_scan/sslyze_securecodebox_io.yaml
7682# Then get the current State of the Scan by running:
7783kubectl get scans
7884```
You can’t perform that action at this time.
0 commit comments