Pixie does not work on Minikube on Mac M1 machines

[PSalant726]

Describe the bug When attempting to deploy Pixie to a new cluster created using minikube, the px deploy command times out at the step labeled "Waiting for Cloud Connector to come online".

To Reproduce Steps to reproduce the behavior:

1. minikube start --driver=qemu2 --cni=flannel --cpus=4 --memory=8000 -p=test

   $ minikube start --driver=qemu2 --cni=flannel --cpus=4 --memory=8000 -p=test
   😄  [test] minikube v1.26.1 on Darwin 13.0 (arm64)
   ✨  Using the qemu2 (experimental) driver based on user configuration
   👍  Starting control plane node test in cluster test
   🔥  Creating qemu2 VM (CPUs=4, Memory=8000MB, Disk=20000MB) ...
   🐳  Preparing Kubernetes v1.24.3 on Docker 20.10.17 ...
       ▪ Generating certificates and keys ...
       ▪ Booting up control plane ...
       ▪ Configuring RBAC rules ...
   🔗  Configuring Flannel (Container Networking Interface) ...
   🔎  Verifying Kubernetes components...
       ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
   🌟  Enabled addons: storage-provisioner, default-storageclass
   🏄  Done! kubectl is now configured to use "phil-test" cluster and "default" namespace by default
   

   • Note the qemu2 driver. The hyperkit driver is not available for M1 Macs:

     $ minikube start --driver=hyperkit --cni=flannel --cpus=4 --memory=8000 -p=test
     😄  [test] minikube v1.26.1 on Darwin 13.0 (arm64)
     ✨  Using the hyperkit driver based on user configuration
     
     ❌  Exiting due to DRV_UNSUPPORTED_OS: The driver 'hyperkit' is not supported on darwin/arm64
     

2. minikube profile test

   $ minikube profile test
   ✅  minikube profile was successfully set to test
   

3. px deploy

   $ px deploy
   Pixie CLI
   
   Running Cluster Checks:
    ✔    Kernel version > 4.14.0
    ✕    Cluster type is supported  ERR: Unrecognized minikube driver. Please use kvm2 or HyperKit instead.
   Check pre-check has failed. To bypass pass in --check=false. error=Unrecognized minikube driver. Please use kvm2 or HyperKit instead.
   

4. px deploy --check=false

   $ px deploy --check=false
   Pixie CLI
   Installing Vizier version: 0.11.9
   Generating YAMLs for Pixie
   Deploying Pixie to the following cluster: test
   Is the cluster correct? (y/n) [y] : y
   Found 1 nodes
    ✔    Installing OLM CRDs
    ✔    Deploying OLM
    ✔    Deploying Pixie OLM Namespace
    ✔    Installing Vizier CRD
    ✔    Deploying OLM Catalog
    ✔    Deploying OLM Subscription
    ✔    Creating namespace
    ✔    Deploying Vizier
    ⠸    Waiting for Cloud Connector to come online
   FATA[0388] Timed out waiting for cluster ID assignment
   

Expected behavior The px deploy command should succeed, with or without the --check=false option, while using the qemu2 driver on an M1 mac.

Screenshots See output inline above.

Logs Please attach the logs by running the following command:

./px collect-logs

Logs were provided to @htroisi via Slack, and deemed unhelpful.

App information (please complete the following information):

• Pixie version

  Pixie CLI
  0.7.17+Distribution.2f3f26c.20220803165147.1.Homebrew
  

• K8s cluster version

  $ kubectl version --short
  Client Version: v1.24.3
  Kustomize Version: v4.5.4
  Server Version: v1.24.3
  

• Node Kernel version

  • Unsure

• Browser version

  • Firefox Developer Edition 104.0b9 (64-bit)

Additional context The hyperkit driver is not available for macOS machines on the ARM64 architecture (M1 Macs). Ideally another driver should be recommended in the minikube install guide, and supported throughout the application. See kubernetes/minikube#11885 for additional context.

[zasgar]

Related to: https://github.com/kubernetes/minikube/issues/11725 And #147