Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

Commit 1aa3dba

Browse files
committed
Add additional install and useage examples
1 parent bd6c9cf commit 1aa3dba

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,8 @@ There is a german article about [Security DevOps – Angreifern (immer) einen Sc
5656
# Deploy secureCodeBox Operator
5757
kubectl create namespace securecodebox-system
5858
helm -n securecodebox-system install securecodebox-operator ./operator/
59+
# The Operator Deployment might fail if the minio instance takes to long to start up
60+
# When this happens re-trigger the Operator deployment by running "kubectl -n securecodebox-system rollout restart deployment securecodebox-controller-manager"
5961

6062
# Elasticsearch Persistence Provider Deployment
6163
helm install persistence-elastic ./persistence/persistence-elastic/
@@ -67,6 +69,13 @@ kubectl apply -f integrations/nmap/nmap-scan-type.yaml -f integrations/nmap/nmap
6769
kubectl apply -f integrations/ssh_scan/ssh-scan-scan-type.yaml -f integrations/ssh_scan/ssh-scan-parse-definition.yaml
6870
kubectl apply -f integrations/sslyze/sslyze-scan-type.yaml -f integrations/sslyze/sslyze-parse-definition.yaml
6971
kubectl apply -f integrations/zap/zap-scan-type.yaml -f integrations/zap/zap-parse-definition.yaml
72+
73+
# Now everything is installed. You can try deploying scans from the `operator/config/samples/` directory
74+
75+
# E.g. www.securecodebox.io sslyze scan
76+
kubectl apply apply -f operator/config/samples/execution_v1_scan/sslyze_securecodebox_io.yaml
77+
# Then get the current State of the Scan by running:
78+
kubectl get scans
7079
```
7180

7281
## How does it work?

0 commit comments

Comments
 (0)