Search
60 results for “irfanhakim”
-
Updated #Orked, my collection of scripts to help set up a production-ready #RKE2 #Kubernetes cluster in your #homelab. This update brings general improvements to the scripts, improved documentation, #HAProxy load balancer support for load balancing multiple Master nodes, and upgraded all components including RKE2, #Longhorn, #Nginx Ingress, #Cert-manager, #MetalLB, #Rancher, etc. to their latest versions.
I still hope someday to support more Kubernetes distributions like #k3s, but haven't gotten around to it. I've also been planning to support more #Linux distros as the base too, instead of only #RockyLinux/#RHEL, but that'll have to wait as well for now. Regardless, I am quite happy with how mature and stable these scripts have turned out to be. If you'd like to set up a cluster of your own, maybe check it out!
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/orked/pull/41 -
Updated #Orked, my collection of scripts to help set up a production-ready #RKE2 #Kubernetes cluster in your #homelab. This update brings general improvements to the scripts, improved documentation, #HAProxy load balancer support for load balancing multiple Master nodes, and upgraded all components including RKE2, #Longhorn, #Nginx Ingress, #Cert-manager, #MetalLB, #Rancher, etc. to their latest versions.
I still hope someday to support more Kubernetes distributions like #k3s, but haven't gotten around to it. I've also been planning to support more #Linux distros as the base too, instead of only #RockyLinux/#RHEL, but that'll have to wait as well for now. Regardless, I am quite happy with how mature and stable these scripts have turned out to be. If you'd like to set up a cluster of your own, maybe check it out!
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/orked/pull/41 -
Updated #Orked, my collection of scripts to help set up a production-ready #RKE2 #Kubernetes cluster in your #homelab. This update brings general improvements to the scripts, improved documentation, #HAProxy load balancer support for load balancing multiple Master nodes, and upgraded all components including RKE2, #Longhorn, #Nginx Ingress, #Cert-manager, #MetalLB, #Rancher, etc. to their latest versions.
I still hope someday to support more Kubernetes distributions like #k3s, but haven't gotten around to it. I've also been planning to support more #Linux distros as the base too, instead of only #RockyLinux/#RHEL, but that'll have to wait as well for now. Regardless, I am quite happy with how mature and stable these scripts have turned out to be. If you'd like to set up a cluster of your own, maybe check it out!
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/orked/pull/41 -
Updated #Orked, my collection of scripts to help set up a production-ready #RKE2 #Kubernetes cluster in your #homelab. This update brings general improvements to the scripts, improved documentation, #HAProxy load balancer support for load balancing multiple Master nodes, and upgraded all components including RKE2, #Longhorn, #Nginx Ingress, #Cert-manager, #MetalLB, #Rancher, etc. to their latest versions.
I still hope someday to support more Kubernetes distributions like #k3s, but haven't gotten around to it. I've also been planning to support more #Linux distros as the base too, instead of only #RockyLinux/#RHEL, but that'll have to wait as well for now. Regardless, I am quite happy with how mature and stable these scripts have turned out to be. If you'd like to set up a cluster of your own, maybe check it out!
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/orked/pull/41 -
I've finally completed most of the guides I was planning on adding to my #Homelab Wiki - now it's got guides on setting up #Portainer, #Immich, #Jellyfin, #ErsatzTV, #OpenMediaVault (#OMV), and even #HomeAssistant - all of these (besides Jellyfin and ErsatzTV, those are on #Proxmox) are hosted on my #RaspberryPi in my homelab.
Most importantly though, I've organised the wiki a lil better - into different courses. The first course details the type of hardware you're going to want to assemble - a beefy server (with only consumer parts) or a mini server (i.e. an #SBC), or whether you'd like to deploy a #NAS, followed by a course to setting up and managing a hypervisor (including #ESXi, but really, use Proxmox - which is #FOSS and plain better).
There's also a whole course on all sorts of 'host deployment environments' (i.e. where your application is hosted on, like #VM, #Docker, #Kubernetes, and #LXC) you could have in your homelab. (One of the) Most importantly, a course on networking - which covers valuable topics like setting up a domain, free or paid, and setting up a reverse proxy for serving your hosted applications publicly, securely.
There's still some stuffs I gotta add, like a complete guide on setting up #TrueNAS (which I've set up for many years at this point, without much documentation on how I did it - so I gotta find an opp to replicate it, when I have extra hardware maybe), but I'm pretty happy with it at this point. If you're planning to get into homelabbing, or even if you're already in it - maybe check it out :blobfoxcat:
🔗 https://github.com/irfanhakim-as/homelab-wiki
RE: https://sakurajima.social/notes/a9so79m6ze -
My #homelab wiki is getting really complicated to organise and write for haha, but it's definitely getting more interesting topics like more #RaspberryPi stuffs, #Docker, and some cool stuffs like #OpenMediaVault and #HomeAssistant. I'm taking my sweet time to update them 'properly' and hope it'll all link/piece together sensibly in the end.
This is partially thanks to me embracing the fact that I just don't (yet) have the resources for a standalone 'mega' homelab (#Proxmox & #Kubernetes based) server cluster that I could simply throw everything to it, hence supplementing that setup with tinier SBC-based servers. Gives me a bit of peace of mind too that things are now more 'spread out'.
The most interesting bit will probably be when I manage to explore replicating a mini version of my #RKE2 Kubernetes cluster, on a single (or at most, two) Raspberry Pi node - maybe based on #k3s, assuming that's better. I'm just not there yet cos I'm kinda reluctant if using something like #k8s on RPi makes much sense since I'm expecting a lot of resources will be wasted that way, when hosting on Docker alone (i.e. on #Portainer) should be leaner.
🔗 Anyway, if y'all wanna keep an eye on it: https://github.com/irfanhakim-as/homelab-wiki -
I've mentioned before that the #Apple Magic #Trackpad 2's one of the best purchases I've ever made, and how perfect it is OOTB on #Linux - gestures and all. The only downside to it is that it's pretty pricey, esp the Black version that I got (tho I still think it's worth every penny).
Since then, I've been meaning to find any other cheaper alternatives to it cos I genuinely think switching from a (wireless) mouse to a trackpad has done wonders to just how nice it is to use and work on my desktop. Surprisingly and disappointingly, none of the known brands seems to bother to be in this market space besides Apple, not even #Logitech (who typically tends to be everywhere).
Right when I thought I was SOL, I discovered a bunch of Chinese #touchpad s - a lot of which are Magic Trackpad clones.. including this one I settled on, the #JOOMA KB96. It not only looks similar to the Apple MT2, it has pretty much the exact same dimensions - surprisingly its glass surface also feels exactly the same as Apple's trackpads.
It tracks just as well too, and all my gestures (2, 3, 4-finger, etc.) work perfectly. Its connectivity options is better than the Apple MT2 even - supporting Wired USB-C, Bluetooth, and even a Wireless USB-A dongle (with USB-C adapter). The only downside to it is that unlike the Apple MT2 which supports clicks (in addition to taps) anywhere on the surface of the trackpad with really nice haptic feedback, this trackpad doesn't support clicks at all - only taps. This shouldn't matter for most people who's used to or even prefers taps though - double tap dragging and triple tap highlighting should be your bestie.
Unlike Apple's Magic Trackpad, it doesn't work OOTB on Linux - but fixing that is super, duper easy thanks to others who's discovered how to before. I've linked my own writing on how to do it on my Linux Wiki below. All in all, for just ~145 MYR (~34 USD) instead of Apple MT2's price tag of 599 MYR (~141 USD), this is quite a banger peripheral to pair with the budget alternative to Apple's Magic Keyboard I've posted about before.
🔗 https://www.aliexpress.com/item/1005008016979688.html
🔗 https://github.com/irfanhakim-as/linux-wiki/blob/master/topics/touchpad.md#apple-magic-trackpad-clone
🔗 https://sakurajima.social/notes/a3k4a7qgb3 -
Still in my painful journey of building my #RaspberryPi 4 #NAS with #OpenMediaVault lol, on today's episode:
My setup is comprised of:
- Pi 4 (4GB)
- SD card for boot storage
- USB Drive for backup (USB 3)
- USB 3 cable -> External powered USB 3 hub -> 3 SATA SSDs via SATA-USB3 cables (USB 3)
- Other USB 2 ports are not occupied
When I boot it up (on #Raspbian Lite, #OMV installed), if I do alsblk, all drives show up incl. USB stick and all 3 SATA SSDs. But when I hop on to OMV > Storage > Disks, it takes a long time to scan/list down all attached storage, and it might do in the end... BUT it will end with all my USB stick AND 3 SATA SSDs crashing/disappearing from my Pi (i.e. no longer show up inlsblk).
What could be the cause, and could it be 'fixed'? Trying to figure out the limitation of the Pi 4 here.. I'm not sure if it's an issue with the USB-SATA cable, the USB hub, the power supply I bought (separately) for the USB hub, or wtv else?
🔗 https://gist.github.com/irfanhakim-as/b6c2a4f9582adc80a4cdd4d408f9c3f7 (logs) -
I have finally caved in and dove into the rabbit hole of #Linux Container (#LXC) on #Proxmox during my exploration on how to split a GPU across multiple servers and... I totally understand now seeing people's Proxmox setups that are made up exclusively of LXCs rather than VMs lol - it's just so pleasant to setup and use, and superficially at least, very efficient.
I now have a #Jellyfin and #ErsatzTV setup running on LXCs with working iGPU passthrough of my server's #AMD Ryzen 5600G APU. My #Intel #ArcA380 GPU has also arrived, but I'm prolly gonna hold off on adding that until I decide on which node should I add it to and schedule the shutdown, etc. In the future, I might even consider exploring (re)building a #Kubernetes, #RKE2 cluster on LXC nodes instead of VMs - and if that's viable or perhaps better.
Anyway, I've updated my #Homelab Wiki with guides pertaining LXCs, including creating one, passing through a GPU to multiple unprivileged LXCs, and adding an #SMB share for the entire cluster and mounting them, also, on unprivileged LXC containers.
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc -
My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉
Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.
Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.
I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.
🔗 https://github.com/irfanhakim-as/charts/pull/136 -
My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉
Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.
Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.
I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.
🔗 https://github.com/irfanhakim-as/charts/pull/136 -
My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉
Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.
Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.
I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.
🔗 https://github.com/irfanhakim-as/charts/pull/136 -
My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉
Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.
Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.
I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.
🔗 https://github.com/irfanhakim-as/charts/pull/136 -
My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉
Previously, it supports #Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.
Now, to reduce reliance on Plex and lean towards a completely #FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.
I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my #Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.
🔗 https://github.com/irfanhakim-as/charts/pull/136 -
#Netdata has saved my butt - I'd only set it up to get temp monitoring for my #homelab, but today I woke up with an alert notifying me that one of my #Proxmox node's #ZFS pool has degraded.
Opening up my Proxmox web interface, checking the main "Summary" and "Disks" tab, nothing would suggest that anything is out of the ordinary - even the failed disk is showing that it had passed its #SMART test. It is only when I dug deeper into the "ZFS" section that I could see that one of my #SiliconPower NVME disk (avoid at all cost btw) has failed and the ZFS pool has degraded.
Fortunately I've an #ADATA SX8200 Pro NVME lying around that I will use as the replacement disk, I've never done this outside of #TrueNAS's web UI, so I'll have to do so while referring to a guide. I'll also link to my guide on setting up Netdata, and will probably write up a guide on how to replace a failed disk in a ZFS pool on my repo after I've done so myself.
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#monitoring
▶️ https://youtu.be/IQA7aTezrVE -
I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.
With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:
- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)
- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes
- Update thehostsfile for strictly necessary name resolution on the Login node and between the Kubernetes nodes
- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.
- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster
- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes
- Deployment and configuration of #MetalLB as the cluster's load-balancer
- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster
- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare
- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster
Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).
If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.
Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.
I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!
If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/charts -
I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.
With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:
- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)
- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes
- Update thehostsfile for strictly necessary name resolution on the Login node and between the Kubernetes nodes
- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.
- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster
- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes
- Deployment and configuration of #MetalLB as the cluster's load-balancer
- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster
- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare
- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster
Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).
If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.
Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.
I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!
If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/charts -
I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.
With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:
- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)
- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes
- Update thehostsfile for strictly necessary name resolution on the Login node and between the Kubernetes nodes
- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.
- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster
- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes
- Deployment and configuration of #MetalLB as the cluster's load-balancer
- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster
- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare
- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster
Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).
If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.
Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.
I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!
If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/charts -
I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.
With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:
- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)
- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes
- Update thehostsfile for strictly necessary name resolution on the Login node and between the Kubernetes nodes
- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.
- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster
- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes
- Deployment and configuration of #MetalLB as the cluster's load-balancer
- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster
- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare
- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster
Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).
If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.
Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.
I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!
If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/charts -
I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.
With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:
- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)
- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes
- Update thehostsfile for strictly necessary name resolution on the Login node and between the Kubernetes nodes
- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.
- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster
- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes
- Deployment and configuration of #MetalLB as the cluster's load-balancer
- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster
- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare
- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster
Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).
If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.
Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.
I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!
If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/charts -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
🚀 #Plex: The media streaming frontend.
🚀 #Jackett: The intermediary between these services.
🚀 #FlareSolverr (opt): Jackett's helper for circumstances that require it.
🚀 #qBittorrent (opt): #Torrent client.
🚀 #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
🚀 #Radarr: Media management tool for movies.
🚀 #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
🚀 #Plex: The media streaming frontend.
🚀 #Jackett: The intermediary between these services.
🚀 #FlareSolverr (opt): Jackett's helper for circumstances that require it.
🚀 #qBittorrent (opt): #Torrent client.
🚀 #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
🚀 #Radarr: Media management tool for movies.
🚀 #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
🚀 #Plex: The media streaming frontend.
🚀 #Jackett: The intermediary between these services.
🚀 #FlareSolverr (opt): Jackett's helper for circumstances that require it.
🚀 #qBittorrent (opt): #Torrent client.
🚀 #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
🚀 #Radarr: Media management tool for movies.
🚀 #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
🚀 #Plex: The media streaming frontend.
🚀 #Jackett: The intermediary between these services.
🚀 #FlareSolverr (opt): Jackett's helper for circumstances that require it.
🚀 #qBittorrent (opt): #Torrent client.
🚀 #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
🚀 #Radarr: Media management tool for movies.
🚀 #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
🚀 #Plex: The media streaming frontend.
🚀 #Jackett: The intermediary between these services.
🚀 #FlareSolverr (opt): Jackett's helper for circumstances that require it.
🚀 #qBittorrent (opt): #Torrent client.
🚀 #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
🚀 #Radarr: Media management tool for movies.
🚀 #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Might try and get a `.deb` package working/published to the AUR for the first time. #Magewell's USB Capture Utility isn't available on the AUR yet. Never done this before so fingers crossed I don't fuck things up too bad 🤠
-
#Decky loader is so fucking buggy on the #SteamDeck it's nuts. For some bloody reason, it keeps setting my Decky update channel to Prerelease instead of Stable, which was i had set. How tf does this even happen?
-
#FediHire #GetFediHired 🥳
I'm a #Programmer/#SoftwareEngineer. I'm most fluent in #Python, have some basics in #Java and #C++, but I'm also taking up new languages like #Javascript and others in my eternal journey of getting better and minimising the impostor syndrome that befalls pretty much all programmers (I feel). I'm also very experienced in #CloudNative/#DevOps technologies, and have been the one devising solutions and maintaining infrastructure in a fast-paced startup environment in my previous employment.
I'm passionate in what I do and those that know me here or IRL would know that I'm always yapping about the things I'm learning or working on - I love discussing them, and I love helping people out - esp those on the same boat as me.
This passion has led me into writing and maintaining tons of #FOSS projects like Mango: a content distribution framework based on #Django for #Mastodon and #Bluesky that powers various bots of mine like @[email protected] and @[email protected], Charts: a #Helm chart repository for an easy and reproducible deployment strategy for all my projects and everything else I self-host on my #homelab, and Orked: O-tomated #RKE2 distribution, a collection of scripts I wrote that are comprehensively documented to enable everyone to self-host a production-grade #Kubernetes cluster for absolutely free in their homes.
I'm based in Malaysia, but I'm open to just about any on-site, hybrid, or remote job opportunities anywhere. In the meantime though, I'm actively looking for a job in countries like #Japan and #Singapore, in a bid for a desperate lifestyle change. I've linked below my Portfolio (which you too, could self-host your own!), for those who'd wish to connect/learn more of me. Thank you ❤️
🔗 https://l.irfanhak.im/resume -
‘The word Hindu is Arabic. Why don’t they throw it out?’
Prominent historian Irfan Habib tells Al Jazeera that lies and falsehoods are being glorified in textbooks by India’s right-wing government.
#interview #IrfanHabib #history #IndianHistory #muslims #mughals #TipuSultan #textbooks #ahoms #hindutva #BJP #india
https://www.aljazeera.com/news/2023/5/10/qa-the-word-hindu-is-arabic-why-dont-they-throw-it-out
-
‘BeerBiceps’ Interview of J. Sai Deepak Violates Community Standards, But YouTube Won’t Take It Down
There are several instances of fake news, misinformation and hate speech in the video, which has also led to the harassment and cyberbullying of three prominent citizens.
#hindutva #cyberbullying #trolls #JSaiDeepak #RanveerAllahabadia #misinformation #islamophobia #muslims #christians #FarmersProtests #propaganda #RomilaThapar #IrfanHabib #BarkhaDutt #UnionGovt #BJP #SocialMedia #YouTube #google #BigTech #india #history #histodon
https://thewire.in/tech/beerbiceps-j-sai-deepak-youtube-violations