Created attachment 1907546 [details]
KubeVirtComponentExceedsRequestedMemory

Verified with 4.10.5-6
no error message found

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.10.5 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:6351

ha! so now that this if fixed, I'm getting a ton of KubeVirtComponentExceedsRequestedMemory alerts:

$ curl -s -k -H "Authorization: Bearer $(oc -n openshift-monitoring sa get-token prometheus-k8s)" https://$alert_url/api/v2/alerts | jq '.[] | select (.labels.alertname == "KubeVirtComponentExceedsRequestedMemory") | { alert: .labels.alertname, container: .labels.container, pod: .labels.pod }'
{
  "alert": "KubeVirtComponentExceedsRequestedMemory",
  "container": "virt-controller",
  "pod": "virt-controller-756db895dc-67blj"
}
{
  "alert": "KubeVirtComponentExceedsRequestedMemory",
  "container": "virt-api",
  "pod": "virt-api-55c4f45f69-pgkmg"
}
{
  "alert": "KubeVirtComponentExceedsRequestedMemory",
  "container": "virt-operator",
  "pod": "virt-operator-6cdbf79fdc-d65jh"
}
{
  "alert": "KubeVirtComponentExceedsRequestedMemory",
  "container": "virt-operator",
  "pod": "virt-operator-6cdbf79fdc-m9p5z"
}
{
  "alert": "KubeVirtComponentExceedsRequestedMemory",
  "container": "virt-api",
  "pod": "virt-api-55c4f45f69-4s55p"
}

I tried to `customizeComponents`[0] but it didn't take the change. Maybe that option isn't in the `kubevirt.io/v1` API yet? Anyone else seeing these alerts after the update?

[0] https://kubevirtlegacy.gitbook.io/user-guide/docs/operations/customize_components

We have opened BZ for it:
https://bugzilla.redhat.com/show_bug.cgi?id=2078545

oh nice. thanks for the link!