search

admirito / gvm-containers

Greenbone Vulnerability Management Containers
86 stars 58 forks source link

Error: can't get a valid version for repositories postgresql, redis. Try changing the version constraint in Chart.yaml #66

Open abel408 opened 9 months ago

abel408 commented 9 months ago

Following instructions from the readme, I am presented with this error when building: Error: can't get a valid version for repositories postgresql, redis. Try changing the version constraint in Chart.yaml

I can choose a specific postgres or redis version, but end up with a bunch of postgres username/password issues if I end up doing so. For example, if I use the latest postgres and redis chart, gvm complains that it can't find the "postgresql-password" key. This is because there isn't one. There is just a "postgres-password" key. When I created a postgresql-password key, the postgres container reports that the gvmd and gvmduser is incorrect:

2024-01-23 18:47:15.414 UTC [558] FATAL: password authentication failed for user "gvmduser" 2024-01-23 18:47:15.414 UTC [558] DETAIL: Role "gvmduser" does not exist. Connection matched pg_hba.conf line 99: "host all all all md5"

It doesn't look like the gvmd db or gvmduser even exist. I tried creating them myself, but end up with a dba role issue. It's like a giant rabbit hole of issues.

Also, "apiVersion: batch/v1beta1" needs to be updated to "apiVersion: batch/v1" in feeds-sync-cronjob.yaml. I'm beginning to think this project is no longer maintained. How are people deploying greenbone in Kubernetes?

abnerrizzi commented 8 months ago

Same here following the README