Comment by darkwater
6 days ago
Sorry to be blunt but from the messages you have written in this threads it is pretty clear you don't know well enough what you are talking about.A real working Kubernetes cluster has many layers of abstractions and the lower ones are outside Kubernetes completely (i.e. containerd or the Linux kernel itself).
Save the insults. Make points.
mAnY lAyERs aside if it doesn’t actually do anything you have not ported anything.
It has to WORK to be a port.
See the PlayStation emulator example - same thing. The game itself is not ported but it still runs. That’s the point!
> Make points. mAnY lAyERs aside if it doesn’t actually do anything you have not ported anything.
You might consider reflecting on this long thread which seems to be solely about your personal definition of the word "port", and arguing with others that the definition should be what you say.
Particularly because you're now stooping to insulting other HN posters over one technical definition of one word.
I am not redefining what a port is – but you are
No amount of whining is going to change anything.
The only thing that would change my opinion is if it actually worked.
And I don't think I was being insulting at all.
What I replied to:
"pretty clear you don't know well enough what you are talking about" is the real insult in this thread, which is what I called out :) Those statements are so boring and don't prove anything. Anyone can say "You don't know what you are talking about" but he hasn't proven anything. It's just an empty insult.
Making letters lower/upper to stress emphasis in a reply to that is part of conveying that.
You haven't changed my mind at all so far, I still think this doesn't qualify as a port.
Question for you: What would you use this project for in production? How could I replace k8s today with this browser port?
2 replies →
It is porting, and I quote the post
> A partial port of Kubernetes’ “kubelet” binary, enough to run pods and probe them.
> Ports of several Kubernetes “controllers”: pod scheduler, namespace controller, kube-proxy, deployment controller, and a few more.
plus a re-implementation of the CNI and a container runtime.
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.