-
Notifications
You must be signed in to change notification settings - Fork 121
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
Custom serverDefinitions not being displayed in PgAdmin console #193
Comments
Any news about this one? I'm experiencing the same issue. Downgrading to pgAdmin chart v1.13.10 "fixes" the problem for the moment. |
I saw a weird error when I tried to reproduce the issue described here, and since @hhorvat0305 applied it is working in an older version of the chart it had to be an issue in the docker image. Searching on the error: The issue is resolved in the latest tag, so either we wait for the 6.20 release or you adjust your values file to use the latest tag rather then 6.19 tag. |
Thanks @rowanruseler will try updating to the latest tag and report back |
this didn't resolve the import issue for me - i'll dig a bit more and report back |
@smitphilip Were you able to solve the problem? Unfortunately I have the same problem |
Describe the bug
Custom serverDefinitions not being displayed in PgAdmin console
Version of Helm and Kubernetes:
Kubernetes (AKS): v1.24.9
Helm: v3.8.0
Which chart:
pgadmin4 (v1.14.3)
What happened:
Once instance has been deployed, validated that servers.json file is indeed mounted into the pod. To confirm that the output file is valid, I saved it to my local machine and was able to re-import the file with no issues. Is this a file permission problem perhaps? I tried setting
VolumePermissions.enabled
to true but that did not make any difference.What you expected to happen:
Server should appear in the PgAdmin console
How to reproduce it (as minimally and precisely as possible):
Not sure exactly?
Anything else we need to know:
The text was updated successfully, but these errors were encountered: