While using KIM inside Rancher Desktop I encountered the following panic. I've not traced the issue, yet, but wanted to report it. We use KIM as part of our setup process to make sure the builder is present.
@mattfarina this looks like improper handling of the case (in my code) where the supplied node selector nets zero results. Is desktop running kim builder install --selector=<something>?
While using KIM inside Rancher Desktop I encountered the following panic. I've not traced the issue, yet, but wanted to report it. We use KIM as part of our setup process to make sure the builder is present.