There’s at least one test (the persistent volumes one) that relies on some Minikube functionality because we run integration tests for our $dayjob Spark image builds using Docker for Desktop instead and that one test fails because it relies on some minikube specific functionality. That test could be refactored because I think it’s just adding a minimal Ceph cluster to the K8S cluster which can be done to any K8S cluster in principal
Rob From: shane knapp ☠ <[email protected]> Date: Wednesday, 14 April 2021 at 18:56 To: Frank Luo <[email protected]> Cc: dev <[email protected]>, Brian K Shiratsuki <[email protected]> Subject: Re: [SPARK-34738] issues w/k8s+minikube and PV tests On Wed, Apr 14, 2021 at 10:32 AM Frank Luo <[email protected]> wrote: Is there any hard dependency on minkube? (i.e, GPU setting), kind (https://kind.sigs.k8s.io/) is a stabler and simpler k8s cluster env on a single machine (only requires docker) , it been widely used by k8s projects testing. there are no hard deps on minikube... it installs happily and successfully runs every integration test except for persistent volumes. i haven't tried kind yet, but my time is super limited on this and i'd rather not venture down another rabbit hole unless we absolutely have to.
