Kubernetes runs on the infrastructure where your services are deployed.

That is not happening here. This is a simulation of a web based kubernetes control plane.

The whole point of the movement toward Docker/kubernetes is that you can run services anywhere without needing a 1:1 OS/physical machine configured for that service. It's an evolution on hijacking VMs for this use case. Consider what this technology is, and is for.

To say it has been ported to the browser would mean I could run e.g. postgres service in my browser the same way installing kubernetes on some cloud provider lets me run it there without having access to that machine directly.

He hasn't ported kubernetes to a browser. If I use some cloud provider UI to configure kubernetes I would not say that k8s is running in that browser tab. I'd just be using a web based dashboard.

Yes it can visualize activity, logs, etc. but kubernetes is not actually provisioning, managing state, scheduling, etc. in its environment (the browser) the way it did in an OS environment. And correct me if I'm wrong - but it's not even calling out to other environments - these are mere simulations of services that aren't running anywhere. Aren't they?

It wouldn't be impossible to do what the title implies is happening - See JSLinux to actually see Linux in a browser. It aint pretty, but that's the kind of thing I'd think of if somebody said they ported kubernetes to the browser. I should be able to run stuff there.