As I take the deep dive into kubernetes what I’m finding is, though definitely a container management system, it can also been seen as a controller yaml processing engine. Let me explain.
Kubernetes understands what a deployment is, and what a service is, these are defined as yaml and loaded. Deployments and services can be seen as controllers which understand those types of objects defined in yaml.
What is interesting about this is that we can implement our own controllers. For example, I could implement a controller that understands how to manage a tic-tac-toe game. That controller could also implement an ai that knows how to play the game. In the same way you can edit a deployment you could edit the game and the kubernetes infrastructure could respond to the change. Or, a move could be another type recognized by the game controller, so you could create a move associated with a game in the same way you can create a service associated with a deployment.
You can imagine doing a ‘k get games’ and seeing the games being played listed out. As well as ‘k describe game a123’ to get the details and status of the game.
Seems I’m not the only one who has started thinking down this line. A quick Google search reveals agones.
This is fascinating and gives me a lot of ideas on how I might reimplement my list processing server & generic game server, within the kubernetes framework.
My first helm chart, a fun milestone. Used it to install my new docker container uploaded to quay.io this morning.
Nice feeling to give back to the open source community.
Now to automate:
* watch for wireguard updates & release an updated docker image
* watch for a centos-8-stream update & release an updated docker image
* watch for a helm chart update & update what is necessary for those changes to be seen
But first, time to investigate and implement longhorn.
A wireguard container built for centos-8-stream which takes advantage of the scripts from the linuxserver docker-wireguard project.
LinuxServer docker-wireguard project: https://github.com/linuxserver/docker-wireguard
To use simply replace the docker-wireguard image with: quay.io/lknight/docker-wireguard-centos-8-stream:latest
Note: Initial startup may take quite awhile, 4 minutes +, if the wireguard module is being recompiled. Be sure to use a volume for the modules folder to avoid having to recompile.
Only useful to those who use the Ivanti Service Desk product, but for those folks, so useful!
The service desk has a button which when clicked generates a popup dialog with a URL pointing directly to the ticket. But who wants to click, then double click to highlight the uri, then use a menu or type a command to copy when all this can be done in just one click. Another first world problem solved.
Wouldn’t be the first time, here’s how that process looks:
As a means to socialize, when asked if I game I say yes but it is only a partial truth. The truth is I write bots to play games, and lately, the only game I play is the stock market.
… and c# just keeps getting better and better.
A project to provide a single REST API & WebSocket interface for the purpose of developing algorithmic stock trading bots.
When you have a website which updates using a websocket, but you do not have direct access to the websocket, you can use the following technique to catch when the DOM is updated: