-
Notifications
You must be signed in to change notification settings - Fork 93
_Scaling Black Duck v0
Important Note: The procedure described on this page has been deprecated.
This page describes how to configure Black Duck to use persistent volume claims in Kubernetes/OpenShift when Black Duck is not deployed with Synopsys Operator.
Do not use these instructions for Black Duck instances deployed with Synopsys Operator.
The documentation below is provided only for historical purposes, and should not be followed unless instructed to by Synopsys support personnel.
This page describes how to permanently set the maximum number of Job Runners and Hub Scans after you have installed Black Duck using kubectl edit.
To use kubectl edit, use a command of the form:
kubectl edit rc jobrunner
kubectl edit rc hub-scan
The kubectl edit commands above will launch an editor (vi by default) to edit the configurations (expressed in YAML by default). In this case, you'll need to edit the "replicas" value and save the configuration.