-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot deploy on on-premise k8s #386
Comments
Thanks for the quick reply. I'm indeed running k8s 1.25.1:
And in case it matters, the helm version:
It looks like it's exactly the issue described in #385. |
There doesn't appear to be a fixed release cadence, but support for 1.25 appears to have been added: zalando/postgres-operator#1999 |
Hi all!
I'm running into issues installing the helm chart on my on-prem/local kubernetes cluster. I'll first dump all relevant manifests, and then describe the issue I'm running into.
Helm values
galaxy-data PVC definition
I use the NFS backed PVC since my "standard" sc (jiva) doesn't support RWX.
Running
helm install -n galaxy my-galaxy -f galaxy-values.yaml galaxy-helm/galaxy/
results inLooks reasonable to me. However, the job my-galaxy-init-db fails in container galaxy-init-postgres, related to permission denied to
chown 101:101 /galaxy/server/database
. Easy enough to fix: wipe the namespace, recreate the NFS share, create that folder with correct ownership in the NFS share, and reinstall the helm chart.Next issue has me stumped though
kubectl logs -n galaxy jobs/my-galaxy-init-db-hb4hl -c galaxy-init-postgres
:And
kubectl logs -n galaxy jobs/my-galaxy-init-db-hb4hl
has a python traceback resulting insqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL: password authentication failed for user "galaxydbuser"
. On the NFS share, the folderserver/database
remains empty.The postgres service pod is running:
kubectl logs -n galaxy pods/galaxy-my-galaxy-galaxy-postgres-0
kubectl logs -n galaxy pods/my-galaxy-galaxy-postgres-7c897bf6c-dd7tb
Any help would be much appreciated :)
The text was updated successfully, but these errors were encountered: