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

Capital letters in username makes the operator crash #2845

Open
Shashankft9 opened this issue Jan 17, 2025 · 0 comments
Open

Capital letters in username makes the operator crash #2845

Shashankft9 opened this issue Jan 17, 2025 · 0 comments

Comments

@Shashankft9
Copy link

Shashankft9 commented Jan 17, 2025

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.12.0
  • **Where do you run it - self hosted kubernetes on vmware provisioned infra
  • Are you running Postgres Operator in production? yes
  • Type of issue? Feature request

When I deploy a postgres cluster with a username containing capital letters, postgres operator faces runtime panic errors which makes the operator go into CrashLoopBackOff state, so even if one cluster has this issue in the CR, ultimately the operator will stop managing the lifecycle of all the clusters which shouldnt be the case.
Can this flow be improved?

One temporary fix I can think of is writing a gatekeeper validation policy, but then I think this is something that should be handled in the codebase of operator. Let me know if maybe I am overlooking something, happy to check the issue or reproduce the issue for easier understanding, can help with fixing this in oss as well if its something the maintainers think should be fixed.

maybe something relevant: https://www.postgresql.org/docs/7.0/syntax525.htm#:~:text=Names%20in%20SQL%20must%20begin,%2D9)%2C%20or%20underscores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant