[Question] Configurable Resources on the OMSAgent/Monitoring Addon #3048
Open
Description
Describe scenario
In some of our AKS clusters, following the activation of many new prometheus metrics endpoints, we are seeing omsagents pods being killed randomly for high memory usage. (looks like it's related to #2125)
Question
When the omsagent damonset is deployed using the addonProfiles in an ARM template, are the resources (memory/cpu limits/requests) configurable in some way on the daemonset?