Skip to content

Conversation

mortenlj
Copy link

Instead of doing a string compare on the username, check the actual namespace of the user to determine if an owner reference can be created.

I believe this should fix #2910

@zalando-robot
Copy link

Cannot start a pipeline due to:

No accountable user for this pipeline: no Zalando employee associated to this GitHub username

Click on pipeline status check Details link below for more information.

Instead of doing a string compare on the username, check the actual namespace of the user to determine if an owner reference can be created.
@mortenlj mortenlj force-pushed the skip-ownerreference-for-prepareddatabase-secret-namespace branch from 4dc43db to 64215b0 Compare June 3, 2025 07:59
@zalando-robot
Copy link

Cannot start a pipeline due to:

No accountable user for this pipeline: no Zalando employee associated to this GitHub username

Click on pipeline status check Details link below for more information.

@FxKu FxKu added this to the 1.15.0 milestone Jul 15, 2025
@FxKu FxKu added the bugfix label Jul 15, 2025
@FxKu FxKu moved this to Good state for merge in Postgres Operator Jul 15, 2025
@FxKu
Copy link
Member

FxKu commented Jul 15, 2025

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Good state for merge
Development

Successfully merging this pull request may close these issues.

Operator fails to create secret in separate namespace when using ownerReferences and preparedDatabases
3 participants