If you ever installed a Kubernetes cluster, you probably know that the minimal setup is composed of 2 nodes: a Control Plane Node (previously called master) and a Worker Node. This is a good thing as we usually don’t want workloads interfering with the API in production environments.
But what about lab environments where you want to run everything in a single VM for example? Well, it’s absolutely possible and actually very simple to configure a Control Plane Node to also accept workloads (pods).
This is managed by “taints”, which is a configuration string applied to nodes. On your Control Plant Node, you can see this by running:
# kubectl describe nodes YourNodeName | grep Taints
It will give you back a string resembling “node-role.kubernetes.io/master:NoSchedule”. NoSchedule, the name says it all.
Well, you can simply remove this taint by running the following command, note the “-” at the end to remove the taint:
kubectl taint nodes YourNodeName node-role.kubernetes.io/master:NoSchedule-
And that’s it, you can now run workload pods on your Control Plane Node in your lab.
This post has nothing to do with the usual content of this website (not K6 related) but I’m sharing my experience of configuring a CentOS Stream 8 Linux software RAID 1 installation on an UEFI system that actually boots when you replace a failed disk.
Most of the tutorials and articles online are about such installations where the the disks are in MBR (legacy) mode and not GPT (UEFI) and this has a huge impact on how your system boots and how you act when a disk fails. We’ll have a look at a scenario where we:
- Start by installing CentOS Stream 8 in software RAID 1 (on 2 disks) mode
- Simulate the failing of one drive
- Replace the drive so the RAID arrays are synchronized again
- Configure the UEFI to be able to boot on this new replacement drive
For demonstration purposes, this will be done using a VM in VirtualBox, but it also applies to any PC or Server booting in UEFI mode, as most machines do nowadays.
One of the hardest things to get right when currently installing a K6 machine is to have a working Windows/DirectX/Drivers combination. Well after some sweat I’m happy to say that I finally found the perfect sweet-spot:
- Windows 2000 with unofficial SP5
- nVidia GeForce FX 5700 with series-50 drivers
- DirectX 9.0c from july 2006 (later versions may require SSE and crash on a K6 without telling you that)
This great success has lead to the update of the OS Support page with all the info one may want and need…the system doesn’t BSOD on nv4_disp.dll when running DirectX 8/9 applications and OpenGL also works fine!
If like me you are (or are looking to) running an SATA HDD/SSD in you K6 machine, you are probably wondering if you should buy a dedicated bootable SATA host-bus adapter PCI card or maybe use an IDE to SATA converter to plug your SATA drive on the motherboard’s IDE ports.
A good Promise PCI card will cost you around 30€ and it works flawlessly and performs very well, but what about these adapters from China you can get for 10€? Well, I tested 2 of them; they all use the same chipset and only the PCB differs a bit. Both adapter’s PCB look like shit with soldering marks all over the place; they are cheaply made but at first glance they work well.
Unfortunately, they perform horribly bad to the point where I had the feeling my K6 system was 4-5 slower doing any action using the disk…so do yourself a favour and avoid them. Buy a good SATA controller instead!
One of the most frustrating experiences when building an old system is to be able to buy cheap parts but then have to pay a lot for all the shipping costs from different sources and countries…at least this is what I was faced with when building my K6 system :)
Fortunately there are some specialised online shops which actually sell old hardware for a very low price so one can combine shipping costs; I ordered several parts from CBO-DO.de and they are very nice and helpful :)
Today I installed another great game bought from GoG: Stronghold! The development team just released a “brand new” HD version from this 2001 castle RTS and it’s AWESOME.
The original Stronghold, which you also get from GoG for free if you buy Stronghold HD, is limited to a 1024×768 resolution and it is a pain to play it on an actual 1920×1080 display…with Stronghold HD you finally get the full experience!
Unfortunately neither of these 2 versions are playable on a 500 MHz K6-2…even the standard version runs slowly. The original recommended spec for the game in 2001 was a 550 MHz or faster CPU.
Recently I bought Dungeon Keeper 2 from Good Old Games as it’s only around 6$ and I remembered it as a fabulous game. GoG are really awesome people which have ported older games so they run on current OS and it’s completely DRM free. After buying the game you get a simple .exe download without any heavy Steam-like client.
So, why am I telling you this? Well just to let you know the port doesn’t run well at all on a 500 MHz K6-2 system with a GeForce 3 (it ran fine back in 1999) :(
It all has to do with some changes made by GoG to the 3D engine…if you look at the installation folders you’ll have 2 executables.
- DKII.exe : this executable runs “sort of fine” on the K6-2 but the experience isn’t that great and it will eventually lag when the missions become more complex and more enemies are displayed. This is NOT the default .exe run from the shortcut the installer creates
- DKII-DX.exe : this is the executable modified even more by GoG to make it stable on modern Windows, it’s just unplayable on an old computer…just forget it
So unfortunately to get your Dungeon Keeper 2 fix on an older machine from the 500 MHz class with todays updates + drivers + DirectX, the GoG version isn’t good. It runs absolutely fine on any modern PC though!