Michael Schubert

> Which OS are you running this on? Fedora 36 with Postgres 14.3 (the latest version in dnf).

Hey, any news? :) > I'd be happy to get rid of the perl regex If you want, I can test and push an alternative patch and drop the regex.

@alban can you say what steps you took on a fresh Fedora system, would like to add it to the docs.

Personally as a user, I wouldn't want kube-spawn to change my kubectl context.

Once https://github.com/kinvolk/kube-spawn/pull/265 is ready and merged, this can be done by setting `cluster-name: my-default` in the config.

> To check k8s setup? Yes, a minimal script to test everything (that is expected to work) works as expected.

As far as I can see, it doesn't test if the pods/services are actually running and reachable over the network endpoints. IMHO we should test this.

The requirement for `GOPATH` and `CNIPATH` is gone now (after https://github.com/kinvolk/kube-spawn/pull/256). The user is still required to provide the CNI plugins to kube-spawn, but a one time install to `/opt/cni/bin`...

I think what would be nice in terms of UX is to automatically add/remove entries to/from `~/.kube/config` with kube-spawn start/stop. The info message could then tell users how to use...

This way users could also use `kubectl config get-contexts` to learn about existing kube-spawn clusters.