When upgrading k3d cluster to 1.26 in https://github.com/neondatabase/autoscaling/pull/928 k3d cluster nodes are getting renamed into K3s v1.26.15+k3s1 instead of K3s dev.
We rely on this to find containerd socket in e2e tests, so they breaks.
Let's detect if we are running inside k3d cluster using K3s prefix.
When upgrading k3d cluster to 1.26 in https://github.com/neondatabase/autoscaling/pull/928 k3d cluster nodes are getting renamed into
K3s v1.26.15+k3s1instead ofK3s dev. We rely on this to find containerd socket in e2e tests, so they breaks. Let's detect if we are running inside k3d cluster usingK3sprefix.