Closed numa1985 closed 1 month ago
nscuro
commented
1 month ago You need to ensure that the API server process is permitted to read and write files from and to the persistent volume, where both logs and the embedded database are stored.
The values.yaml has an example on how to achieve that via initContainers:
numa1985
commented
1 month ago @nscuro : Thanks .. It worked was able to connect to internal database,but for production we are planning to use microsoftSQLServer database,if we want to add the database connectivity details as shown in below snapshot under api server in values.yaml where should we add.
nscuro
commented
1 month ago See https://docs.dependencytrack.org/getting-started/configuration/#api-server
If properties are specified as foo.bar.baz, their respective environment variable would be FOO_BAR_BAZ.
Example with MSSQL: https://github.com/DependencyTrack/dependency-track/blob/b188c7d919d7fc9568dde86d3e5a29a05ad6f66c/dev/docker-compose.mssql.yml#L23-L27
Closing this issue as the original problem has been resolved.
Hi ,
Pod is going for crashloopback due to issue connecting to database. We are using AKS with Kubernetes version 1.29.2.PFB details.
ubuntu@NARU-Pr5530:~/dtrack$ helm upgrade --install dtrack dependency-track/dependency-track --namespace dtrack --reset-values --values values.yaml Release "dtrack" has been upgraded. Happy Helming! NAME: dtrack LAST DEPLOYED: Wed May 22 11:38:49 2024 NAMESPACE: dtrack STATUS: deployed REVISION: 2 TEST SUITE: None
ubuntu@NARU-Pr5530:~/dtrack$ cat values.yaml apiServer: resources: requests: cpu: "100m" memory: "512Mi" limits: cpu: "1" memory: "512Mi" persistentVolume: enabled: true size: 10Gi extraEnv: SYSTEM_REQUIREMENT_CHECK_ENABLED: "false"
Error info ++++
Thanks