Repository navigation
Remove the unused admin superuser from the managed PostgreSQL - #56
Merged
Merged
Conversation
The managed PostgreSQL got an `admin` user with superuser and createdb rights, and its password in a Secret, although nothing connects with it: the trusted issuers list and the credentials config service have their own users, and the operator already creates its `postgres` superuser. It is no longer created. The operator does not drop roles removed from the manifest, so an existing cluster keeps `admin` until it is dropped by hand (`DROP ROLE admin;`) and its Secret `admin.<cluster>.credentials.postgresql.acid.zalan.do` deleted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mortega5
approved these changes
Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The managed PostgreSQL got an
adminuser with superuser and createdb rights, and its password in a Secret, although nothing connects with it: the trusted issuers list and the credentials config service have their own users, and the operator creates its ownpostgressuperuser. It is no longer created.The operator does not drop roles removed from the manifest, so an existing cluster keeps
adminuntil it is dropped by hand:Tests
helm lintand the kubeconform validation of the shared chart lintpostgresqlresource has thetilandccsusers only