-
Notifications
You must be signed in to change notification settings - Fork 18
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
restrict manager resource cache based on namespaces from environment #186
base: main
Are you sure you want to change the base?
Conversation
tested, peak usage was 50 Mi for startup down from ~ 1.5 Gi on a semi-prod cluster. |
The namespace(s) name needs to be configurable as this operator is developed to work with multiple namespaces https://sdk.operatorframework.io/docs/building-operators/golang/operator-scope/#configuring-watch-namespaces-dynamically is the way we need to look to fix this one. |
Yes, I want to refactor when we actually need it and so reused operator namespace. |
IMO, it should be implemented in the above-requested manner instead of immediately changing it and later refactoring it. @nb-ohad WDYT? |
|
37772c2
to
e69eb50
Compare
done. |
always cache resources from operator deployed namespace and provider an option to user for caching resources from other namespaces via `WATCH_NAMESPACE` env var with a comma separated namespace values. Signed-off-by: Leela Venkaiah G <[email protected]>
always cache resources from operator deployed namespace and provider an option to user for caching resources from other namespaces via
WATCH_NAMESPACE
env var with a comma separated namespace values.fixes: #184