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

Fix default watch namespacing #97

Merged
merged 3 commits into from
Jan 29, 2025
Merged

Fix default watch namespacing #97

merged 3 commits into from
Jan 29, 2025

Conversation

jogrogan
Copy link
Collaborator

@jogrogan jogrogan commented Jan 29, 2025

  • Added consistency for namespace usage between Operator and K8sContext, split usages of namespaces to watch vs expected default namespace to operate within.
  • nit: put KEY columns first for Venice

Copy link
Collaborator

@ryannedolan ryannedolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think making the "namespace" configurable makes sense. There are only two possible situations: the operator is running inside K8s (in which case it will know what namespace to use), or it is running outside. If outside, we already have kube/config, which lets you configure any namespace. I don't think overriding that logic makes sense.

That said, adding a watch argument makes sense. Operators typically do that. I think we should just thread that through to registerInformer rather than muck with K8sContext, since that is meant to be a read-only singleton.

Copy link
Collaborator

@ryannedolan ryannedolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it, thx

@jogrogan jogrogan merged commit 00e7864 into main Jan 29, 2025
1 check passed
@jogrogan jogrogan deleted the jogrogan/namespace branch January 29, 2025 20:37
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.

2 participants