Quake III Arena, K3s and a Raspberry Pi | Hacker News Reader

Quake III Arena, K3s and a Raspberry Pi

johansiebens.dev

81 pointsalexellisuk10 comments

What strikes me about this post is the game immediately invokes fond memories from playing LAN Q3 and UT circa about 20 years ago with curiosity that comes with having yet to mess with Q3A.js mentioned in this article. One of my main rivals from those days of teenage gaming (not much of a rival since he pwned me regularly) went on to earn a number of degrees and ended up working in finance at EA before going into investment banking.

We live in an age of marvels. So many technologies and novelties.

I wonder what today’s “e-sports” champions will do when they “retire” from the game.

He's probably still gaming today. Maybe not at a championship level, but there's a lot less pressure to "drop childish things and stop doing what you enjoy when you become an adult" compared to 20-30 years ago.

Why does this need to play in a web browser? Is there no way to route kube containers to a display device?

I saw "a digitalocean account and API token" and nearly stopped reading...

> Is there no way to route kube containers to a display device?

There's no problem with running a virtual frame buffer in a container and using either something like VNC or X remoting to access its display output. However, accessing it via a web browser, i.e. HTTP, gives you built-in mechanisms for routing incoming requests to a container based on the url, so it might be a bit more convenient to set up.

Afaik standard graphics on cloud hw is not that easy to get today unless you pay for ML instances. However, local hw have better leverage probably.

That's what the virtual frame buffer I mentioned is for. There's no problem running e.g. web browsers in containers on Kubernetes, and accessing their GUI via VNC. That's what testing systems like Selenium Grid do.

However, this example does depend on how much graphics power Quake III needs. Since it was released 21 years ago, I was assuming it doesn't really need a GPU. If CPU-only graphics is enough, it should work fine.

If this needs a digital Ocean server, why not just run the whole thing on that?

You might actually be able to get this to fit into the free tier (https://dev.to/phocks/how-to-get-a-free-google-server-foreve...) of Google's cloud platform so long as it's less than 1GB of traffic in a month.

We took Show HN out of the title because (1) it doesn't look to be your own work? (sorry if I got that wrong), and (2) it's a blog post, not something people can exactly try out or play with.

https://news.ycombinator.com/showhn.html

http://www.quakejs.com

Reply on news.ycombinator.com