Skip to content

Skip creation of OwnerReference if user is in a different namespace #2912

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

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

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.
@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.

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

Successfully merging this pull request may close these issues.

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