Patrick Ohly
Patrick Ohly
Hmm, both works for me (PMEM-CSI test/e2e, using ginkgo v2 v2.1.4). FYI, I have to use this fork of the controller-runtime for that project because otherwise I would be stuck...
> > Which of the two options? -ginkgo.junit or adding some custom GenerateJUnitReport invocation? Either way, that sounds like a bug that should be reported. > > It was reported...
> All packages need to import _ "github.com/onsi/ginkgo/v2", even if they don't contain ginkgo tests when we want to run tests with the ginkgo.junit-report flag. If a package doesn't contain...
> This is really, really bad. Is there any way to fix ginkgo, has this issue bee raised there? This cannot be fixed. The Ginkgo API is designed around global...
> deploy a central provisioner together with a driver component that knows about nodes where the driver runs -> can be done today, but implies that CSI drivers must be...
> do something similar inside external-provisioner, probably based on node labels (specify node selector for "driver not running" and handle those) This is conceptually very similar to setting `AllowedTopologies` in...
> This is conceptually very similar to setting AllowedTopologies in the storage class which uses late binding. The volume scheduler will check that before selecting a node, right? Yes, it...
/remove-lifecycle stale
/remove-lifecycle rotten
/remove-lifecycle stale