[Feature Request] Ability to set PriorityClass for OMSAgent in AKS

[davelosert]

I am not sure if this is the correct repository to open this issue, but:

It would be great if it was possible to somehow configure a priority-class for the omsagent within an AKS-Cluster.

Currently, that does not seem possible - or at least I could find no documentation whatsoever about it.

In our scenario, we want to give the cluster monitoring a somewhat higher priority than most of the other services - so that in case of an error, we won't be flying blind.

The only workaround I can think of is to use a global default class - however that is not really feasible as there might be other, unimportant pods without a PriorityClass within the cluster that might suddenly be ranked way higher than they should be.

Is such a feature possible?

[daweim0]

@davelosert does setting omsagent.priority solve your problem? docs here

We don't support changing the priority class in managed deployments (onboarding a cluster through the azure portal or cli). However, that runs omsagent pods with the system-node-critical priority class, which should be high enough?

(sorry for bringing a year-old issue back to life, I'm doing some cleanup)

[davelosert]

@daweim0 : Thanks for your response and the tip.

However, we switched to another monitoring solution so unfortunately I can not try this out anymore.
Mabye there is someone else who is experiencing the same problem might be able to try and give you a feedback?

[github-actions]

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.

[github-actions]

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