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
For more details on customizing Helm charts, see the [Helm documentation](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing).
18
20
19
21
## Log Levels
22
+
20
23
You can configure the log level for each SBOMscanner component to control the verbosity of the logs.
21
24
22
25
```yaml
@@ -33,9 +36,11 @@ worker:
33
36
Available log levels are: `debug`, `info`, `warn`, `error`.
34
37
35
38
## Resource Limits and Requests
39
+
36
40
Each component has default resource limits and requests that you can customize based on your cluster's capacity and workload requirements.
37
41
38
42
### Controller
43
+
39
44
```yaml
40
45
controller:
41
46
resources:
@@ -48,6 +53,7 @@ controller:
48
53
```
49
54
50
55
### Storage
56
+
51
57
```yaml
52
58
storage:
53
59
resources:
@@ -60,6 +66,7 @@ storage:
60
66
```
61
67
62
68
### Worker
69
+
63
70
```yaml
64
71
worker:
65
72
resources:
@@ -76,9 +83,11 @@ Adjust these values based on your workload. The storage component typically need
76
83
For more information on resource management, see the [Kubernetes documentation on resource requests and limits](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).
77
84
78
85
## PostgreSQL Configuration
86
+
79
87
SBOMscanner requires a PostgreSQL database to store SBOM data. You have two options: use the built-in [CloudNativePG (CNPG) operator](https://cloudnative-pg.io/) or connect to an external PostgreSQL instance.
80
88
81
89
### Using CloudNativePG (Default)
90
+
82
91
By default, SBOMscanner deploys a PostgreSQL cluster using the CloudNativePG operator. This is the easiest way to get started.
83
92
84
93
```yaml
@@ -95,6 +104,7 @@ storage:
95
104
```
96
105
97
106
**Configuration options:**
107
+
98
108
- `instances`: Number of PostgreSQL replicas (default: 3)
99
109
- `storage.size`: Size of the persistent volume. You can increase this value later, and changes will be automatically applied to existing PVCs. Size cannot be decreased. See the [CNPG documentation](https://cloudnative-pg.io/documentation/current/storage/#volume-expansion) for more details.
For more configuration options, refer to the [CloudNativePG Cluster configuration documentation](https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-ClusterSpec).
105
115
106
116
### Using an External PostgreSQL Instance
117
+
107
118
If you already have a PostgreSQL instance or prefer to manage it separately, disable CNPG and provide connection details.
108
119
109
120
```yaml
@@ -118,6 +129,7 @@ storage:
118
129
**Steps to configure external PostgreSQL:**
119
130
120
131
1. Create a `Secret` with the PostgreSQL connection URI:
The URI format follows the [PostgreSQL connection URI specification](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS).
143
+
The URI format follows the [PostgreSQL connection URI specification](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS).
132
144
133
145
> **Note:** Any `sslmode` or other `ssl*` parameters in the URI are ignored.
134
-
> SBOMBastic always enforces CA verification when connecting to the database,
146
+
> SBOMscanner always enforces CA verification when connecting to the database,
135
147
> using the CA certificate specified in the `caSecretName` secret.
136
148
137
149
2. Create a `Secret` with the CA certificate used to verify the PostgreSQL server certificate:
0 commit comments