You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case is quite simple: I have similar instances in different namespaces that need to be removed based on annotations.
In my case, it is common to place an annotation on the namespace itself, which I already do. Additionally, it is essential for the application to query the Kubernetes API only for namespaces. Currently, it queries all resources in the cluster, which creates unnecessary load on the API server (approximately 200 requests every 5 minutes).
To address this, I propose introducing a configuration file that allows specifying a list of kubernetes resources the controller should manage.
Why do you personally want this feature to be implemented?
No response
How long have you been using this project?
No response
Additional information
I can also take it :)
The text was updated successfully, but these errors were encountered:
Describe the feature request
My use case is quite simple: I have similar instances in different namespaces that need to be removed based on annotations.
In my case, it is common to place an annotation on the namespace itself, which I already do. Additionally, it is essential for the application to query the Kubernetes API only for namespaces. Currently, it queries all resources in the cluster, which creates unnecessary load on the API server (approximately 200 requests every 5 minutes).
To address this, I propose introducing a configuration file that allows specifying a list of kubernetes resources the controller should manage.
Why do you personally want this feature to be implemented?
No response
How long have you been using this project?
No response
Additional information
I can also take it :)
The text was updated successfully, but these errors were encountered: