• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

kubevirt / hyperconverged-cluster-operator / 12414707698 / 1
72%
main: 80%

Build:
Build:
LAST BUILD BRANCH: v1-func-tests
DEFAULT BRANCH: main
Ran 19 Dec 2024 02:34PM UTC
Files 72
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

19 Dec 2024 02:27PM UTC coverage: 71.739% (+0.06%) from 71.68%
12414707698.1

Pull #3219

github

orenc1
Handle kubevirt control plane NodePlacement on hypershift clusters

Since kubevirt v1.3, the kubevirt control plane components (e.g. virt-controller and virt-api) are getting schdeuled by default on the control-plane/master
nodes, not regular worker nodes.
In hypershift (Hosted Control Planes) clusters, there are no control plane nodes at all (the control plane is hosted as pods on the management cluster).
Therefore, in case there are no control plane nodes, we're setting the kubevirt's node placement as an empty struct to avoid any predefined scheduling/affinity rules
that might prevent the pods to be scheduled on the cluster.

Signed-off-by: Oren Cohen <ocohen@redhat.com>
Pull Request #3219: Handle kubevirt control plane NodePlacement on hypershift clusters

6138 of 8556 relevant lines covered (71.74%)

0.79 hits per line

Source Files on job 12414707698.1
  • Tree
  • List 0
  • Changed 4
  • Source Changed 0
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 12414707698
  • 3da3ecc9 on github
  • Prev Job for on nodeplacement_no_masters (#12387925425.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc