Skip to content

If no namespace is explicitly set in the kube context, the operator will silently fall back to watch all namespaces #433

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.

Sign up for GitHub

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

Jump to bottom
Closed
metacosm opened this issue Jun 11, 2021 · 0 comments · Fixed by #439
Closed

If no namespace is explicitly set in the kube context, the operator will silently fall back to watch all namespaces #433

metacosm opened this issue Jun 11, 2021 · 0 comments · Fixed by #439
Assignees
@metacosm

Comments

@metacosm
Copy link
Collaborator

There is no way around this but we should at least warn the users about this when the operator starts and document the problem.
@metacosm metacosm self-assigned this Jun 11, 2021
@snowdrop-bot snowdrop-bot mentioned this issue Jun 11, 2021
Closed
metacosm added a commit that referenced this issue Jun 14, 2021
@metacosm
feat: fail if current namespaces is required but cannot be resolved
171640e 
Fixes #433
@metacosm metacosm mentioned this issue Jun 14, 2021
Merged
metacosm added a commit that referenced this issue Jun 14, 2021
@metacosm
feat: fail if current namespaces is required but cannot be resolved
8dd37db 
Fixes #433
metacosm added a commit that referenced this issue Jun 17, 2021
@metacosm
feat: fail if current namespaces is required but cannot be resolved
163643f 
Fixes #433
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@metacosm metacosm

Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@metacosm