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
{{ message }}
Repository navigation
Commit 792aee5
Browse filesBrowse the repository at this point in the historyBrowse files
<li> <b>Increasing cluster resources</b>: Running a lot of pods at the same time can be resource-intensive. If you
381
-
find that your persistence providers are not reacting in appropriate time, you might want to increase the number of
382
-
cpus and memory usage for your minikube cluster: <br />
383
-
<code>
384
-
# If you already created a cluster, you most likely have to delete it at first <br />
385
-
minikube stop <br />
386
-
minikube delete <br />
387
-
# Create a new cluster with more resources <br />
388
-
minikube start --memory 8192 --cpus 4
389
-
</code>
390
-
</li>
391
-
</ul>
341
+
342
+
Connecting the SCB to a persistence provider, especially DefectDojo, can sometimes be a bit tricky. The following tips might help in case that something went wrong:
343
+
344
+
-**Waiting:** It takes some time for the DefectDojo or Kibana instance to come up. You might also have to refresh several times in order to connect to localhost after the port-forward.
345
+
346
+
-**Verbose logging:** You can view verbose output for everything in your cluster, for example via [stern](https://github.com/wercker/stern). For the following steps, you have to have [krew](https://krew.sigs.k8s.io/docs/user-guide/setup/install/#bash) installed:
347
+
348
+
```shell
349
+
kubectl krew install stern
350
+
# View all logs in default namespace:
351
+
kubectl stern .*
352
+
# View for a specific namespace
353
+
kubectl stern .* --namespace scanning
354
+
```
355
+
356
+
-**Re-Installation of DefectDojo:** Note that if anything went wrong, and you have to re-install DefectDojo in the cluster, the _createSecret_ flags in the values.yaml file of DefectDojo must not be set. You can find more details [here](https://github.com/DefectDojo/django-DefectDojo/blob/dev/readme-docs/KUBERNETES.md#re-install-the-chart).
357
+
358
+
-**Server error in DefectDojo:** Make sure that all pods are running. If you are continuing to experience errors after a re-installation, consider using a different cluster manager (e.g., kind instead of minikube).
359
+
360
+
-**Using a local instance of DefectDojo rather than Kubernetes:** If nothing helps, you still have the option to run DefectDojo outside your cluster (instructions [here](https://github.com/DefectDojo/django-DefectDojo#quick-start)). After that, you can connect the DefectDojo hook treating it like a _remote_ instance of DefectDojo. The helm install command for the hook would look like this:
361
+
362
+
```shell
363
+
# $YOURLOCALIP should look something like http://192.168.2.242:8080
-**Increasing cluster resources:** Running a lot of pods at the same time can be resource-intensive. If you find that your persistence providers are not reacting in appropriate time, you might want to increase the number of CPUs and memory usage for your minikube cluster:
369
+
370
+
```shell
371
+
# If you already created a cluster, you most likely have to delete it at first
0 commit comments