i see lots of mentions of hostpath, so, uh, what gives?

hostpath

is not a storage class, but a volume type. Rancher Desktop provides a

local-path

storage class, that is a

local

volume.

same question remains then - why is the error thrown?

Maybe minikube has a

hostpath

storage class? Which would be a confusing name choice...

Well, show your volume definitions; I suspect you specify

hostpath

as a storage class name, which is not defined under

k3s

I do not

volumes:
- name: foobar
  hostPath:
    path: "/tmp/foobar"

It is not called

hostpath

on

minikube

either; it is called

default

there:

$ kubectl get sc
NAME                 PROVISIONER                RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
standard (default)   <http://k8s.io/minikube-hostpath|k8s.io/minikube-hostpath>   Delete          Immediate           false                  27s

🤷

So you need to show an example config that can reproduce the error, if you want some help with finding your problem

i just did. right above?

That is not a complete example that you can pass to

kubectl apply ...

don't worry about it 😉

ok then

cool. very mature.

I've added a working example to your "bug" report. It is a problem with your config. If you are not willing to share it, then there is nothing else I can do to help you.

what ever you say man. if you think this is the way to increase adoption

Sorry, what do you expect me to do? I genuinely have no idea.

it's fine. i was the last rancher hold out. i'm just gonna move to minikube. every one on my team can run this chart with success locally

It's ok. I'm trying to help, but you seemed in a bad mood...