Does KubeVirt install regardless? We have seen in the past this issue, where KubeVirt installs but the error gets logged: #9725

If not, it might help to know your environment details.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

I'm seeing this constant spam in my kube-apiserver logs.

@starcraft66 What version of k8s and kubevirt are you running?

I'm on kubernetes 1.27.8 at the moment.

same here.
k8s 1.26.8
kubevirt 1.1.0

api-logs spammed as hell.

@fossedihelm (since you were also pinged on #9725), are you able to shed any light on this?

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

/remove-lifecycle rotten

checking virt-api pods logs I see:
2024-04-07T09:45:21.077587774Z {"component":"virt-api","level":"info","msg":"setting rate limiter for the API to 5 QPS and 10 Burst","pos":"api.go:1097","timestamp":"2024-04-07T09:45:21.072417Z"}

so virt-api is setting a rate limit of 5 queries per second with a burst of 10.

This is probably exceeded during the installation due to many request in a short sequence, but it simply means that we are hitting the rate limit and the request is delayed by requeuing but this is definitively harmless if the install is then fine.

This is not systematic depending on the speed of the hardware, maybe we can fine-tune the rate limit on virt-api to prevent this noise.

The root cause is missing /openapi/v3 endpoint. It should not have any functional impact. We would welcome a PR if anyone would be interested.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot: Closing this issue.