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

[common] Allow custom postgresGID on cnpg definition. #27350

Open
2 tasks done
nlaille opened this issue Jul 10, 2024 · 4 comments
Open
2 tasks done

[common] Allow custom postgresGID on cnpg definition. #27350

nlaille opened this issue Jul 10, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@nlaille
Copy link

nlaille commented Jul 10, 2024

Is your feature request related to a problem?

I need to be able to set postgresGID in cluster spec for CloudNative PG clusters, otherwise CloudNative PG clusters' pods will inherit the default value (26).
I am using NFS (synology) as storage provider, and the GID 26 doesn't exists and cannot be created.

Describe the solution you'd like

Allow custom postgresGID on cnpg definition.

ClusterSpec for CNPG : https://cloudnative-pg.io/documentation/1.15/api_reference/#ClusterSpec

Describe alternatives you've considered

Create CNPG cluster outside of charts, however some charts (authelia) are relying on cnpg values and cannot be overriden.

Additional context

No response

I've read and agree with the following

  • I've checked all open and closed issues and my request is not there.
  • I've checked all open and closed pull requests and my request is not there.
@nlaille nlaille added the enhancement New feature or request label Jul 10, 2024
@PrivatePuffin
Copy link
Member

Actually, preferably we have it follow the .Values.securityContext setting unless overridden. So it shouldn't be using 26 in the first place.

Though I would HEAVILY advice running postgresql on a NFS backend.

@nlaille
Copy link
Author

nlaille commented Jul 10, 2024

@Ornias1993 , I may have missed something, but even with securityContext set, the cnpg clusters' pods won't inherit it.
It seems that the only way to change the securityContext of cnpg clusters' pods is with postgresUID and postgresGID.

@PrivatePuffin
Copy link
Member

@Ornias1993 , I may have missed something, but even with securityContext set, the cnpg clusters' pods won't inherit it. It seems that the only way to change the securityContext of cnpg clusters' pods is with postgresUID and postgresGID.

That's why I was saying we should implement that instead.

@PrivatePuffin
Copy link
Member

Locked as no use input is required.

@truecharts truecharts locked and limited conversation to collaborators Jul 10, 2024
@truecharts truecharts unlocked this conversation Oct 7, 2024
@PrivatePuffin PrivatePuffin changed the title Allow custom postgresGID on cnpg definition. [common] Allow custom postgresGID on cnpg definition. Oct 7, 2024
@PrivatePuffin PrivatePuffin transferred this issue from another repository Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants