Run fluentd with a custom configuration about docker-provider HOT 6 CLOSED

Hi, @adrianabasoc-uipath , we are working on feature to provide customers to change the data collection settings such as interval and namespaces exclusion for applicable data types such as KubePodInventory, KubeNodeInventory and container inventory etc but not for kube-events. Question, why do you want change the run_interval for kube_events and how does this help?

This ama-logs-rs-configamp not configurable and this needs to be removed from the yaml. if you are interested to try out the cost optimization feature preview, please reach out us on [email protected] with subscription(s) or cluster ids which you want to try.

from docker-provider.

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

from docker-provider.

We would like to change the run_interval for kube_events because when getting the data from k8s it uses lists instead of watches, which is not very efficient.

from docker-provider.

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

from docker-provider.

This issue was closed because it has been stalled for 12 days with no activity.

from docker-provider.

We would like to change the run_interval for kube_events because when getting the data from k8s it uses lists instead of watches, which is not very efficient.

We already implemented watch for the types ( Pod & Node) which were are making high number of APIs call in large cluster. The total number of API calls making from our agent is much smaller what we were making before. We have plan to move to Watch API for remaining resource types as well. changing the run_interval to higher value, will make the events getting lost with list API. is loss of events not an issue for your scenarios?

from docker-provider.