Skip to content
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

[Bug]: LDAP with Pgbouncer #6826

Open
4 tasks done
metalshanked opened this issue Feb 11, 2025 · 0 comments
Open
4 tasks done

[Bug]: LDAP with Pgbouncer #6826

metalshanked opened this issue Feb 11, 2025 · 0 comments
Assignees
Labels
triage Pending triage

Comments

@metalshanked
Copy link

Is there an existing issue already for this bug?

  • I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

  • I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

  • I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

1.25 (latest patch)

What version of Kubernetes are you using?

1.32

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

Using the default pgbouncer Pooler spec and have setup LDAP auth with cnpg.

However, it does not seem to work when clients connect to pgbouncer
Authentication Failed messages even with the correct username and passwords

Note: LDAP works fine when directly connected to the cnpg instance pods

Cluster resource

Relevant log output

Code of Conduct

  • I agree to follow this project's Code of Conduct
@metalshanked metalshanked added the triage Pending triage label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Pending triage
Projects
None yet
Development

No branches or pull requests

2 participants