Fosstodon

MikaI've just merged a huge PR to my <a href="https://sakurajima.social/tags/Orked" rel="nofollow noopener" target="_blank">#Orked</a> (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready <a href="https://sakurajima.social/tags/RKE2" rel="nofollow noopener" target="_blank">#RKE2</a> <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a> cluster in their <a href="https://sakurajima.social/tags/homelab" rel="nofollow noopener" target="_blank">#homelab</a>. 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 <a href="https://sakurajima.social/tags/Helm" rel="nofollow noopener" target="_blank">#Helm</a>, <a href="https://sakurajima.social/tags/Docker" rel="nofollow noopener" target="_blank">#Docker</a>, <a href="https://sakurajima.social/tags/k9s" rel="nofollow noopener" target="_blank">#k9s</a>, <a href="https://sakurajima.social/tags/kubens" rel="nofollow noopener" target="_blank">#kubens</a>, <a href="https://sakurajima.social/tags/kubectx" rel="nofollow noopener" target="_blank">#kubectx</a>, etc.) - Setup passwordless <a href="https://sakurajima.social/tags/SSH" rel="nofollow noopener" target="_blank">#SSH</a> access from the Login node to the rest of the Kubernetes nodes - Update the <code>hosts</code> file 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 <a href="https://sakurajima.social/tags/Longhorn" rel="nofollow noopener" target="_blank">#Longhorn</a> storage, including formatting/configuring their virtual disks on the Worker nodes - Deployment and configuration of <a href="https://sakurajima.social/tags/MetalLB" rel="nofollow noopener" target="_blank">#MetalLB</a> as the cluster's load-balancer - Deployment and configuration of <a href="https://sakurajima.social/tags/Ingress" rel="nofollow noopener" target="_blank">#Ingress</a> <a href="https://sakurajima.social/tags/NGINX" rel="nofollow noopener" target="_blank">#NGINX</a> 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 <a href="https://sakurajima.social/tags/cert-manager" rel="nofollow noopener" target="_blank">#cert-manager</a> to obtain and renew <a href="https://sakurajima.social/tags/LetsEncrypt" rel="nofollow noopener" target="_blank">#LetsEncrypt</a> certs automatically - supports both <a href="https://sakurajima.social/tags/DNS" rel="nofollow noopener" target="_blank">#DNS</a> and HTTP validation with <a href="https://sakurajima.social/tags/Cloudflare" rel="nofollow noopener" target="_blank">#Cloudflare</a> - Installation and configuration of <a href="https://sakurajima.social/tags/csi-driver-smb" rel="nofollow noopener" target="_blank">#csi-driver-smb</a> 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 <a href="https://sakurajima.social/tags/SELinux" rel="nofollow noopener" target="_blank">#SELinux</a> 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 <a href="https://sakurajima.social/tags/RockyLinux" rel="nofollow noopener" target="_blank">#RockyLinux</a> 8+ (should also support any other <a href="https://sakurajima.social/tags/RHEL" rel="nofollow noopener" target="_blank">#RHEL</a> distros such as <a href="https://sakurajima.social/tags/AlmaLinux" rel="nofollow noopener" target="_blank">#AlmaLinux</a>), but I am planning to improve the project over time by adding more <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a> distros, <a href="https://sakurajima.social/tags/IPv6" rel="nofollow noopener" target="_blank">#IPv6</a> support, and possibly even <a href="https://sakurajima.social/tags/K3s" rel="nofollow noopener" target="_blank">#K3s</a> for a more lightweight <a href="https://sakurajima.social/tags/RaspberryPi" rel="nofollow noopener" target="_blank">#RaspberryPi</a> 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 <a href="https://sakurajima.social/tags/mika" rel="nofollow noopener" target="_blank">#mika</a> helm chart repo 🥳 🔗 <a href="https://github.com/irfanhakim-as/orked" rel="nofollow noopener" target="_blank">https://github.com/irfanhakim-as/orked</a> 🔗 <a href="https://github.com/irfanhakim-as/charts" rel="nofollow noopener" target="_blank">https://github.com/irfanhakim-as/charts</a>

MikaUpdate: I've found <a href="https://sakurajima.social/tags/csi-driver-smb" rel="nofollow noopener" target="_blank">#csi-driver-smb</a> which seems to be perfect for my needs, and even a video of someone deploying it to their cluster for <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a>. I've deployed it successfully to my <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a> cluster pretty easily, and am attempting to achieve the same thing but on <a href="https://sakurajima.social/tags/Plex" rel="nofollow noopener" target="_blank">#Plex</a> rather than Jellyfin. Ran into another obstacle tho, while it seems that my <a href="https://sakurajima.social/tags/TrueNAS" rel="nofollow noopener" target="_blank">#TrueNAS</a> <a href="https://sakurajima.social/tags/SMB" rel="nofollow noopener" target="_blank">#SMB</a> share is mounted to the container (shows up in <code>df -h</code>), my root user in the container could not <code>ls</code> the mount point (i.e. <code>/mnt/smb</code>), it'd just return the <code>Permission denied</code> error. Weird thing is the root user could <code>cd</code> into the mount point and its existing subdirectories, but not <code>ls</code> them or write any files to them. I could <code>cat</code> files inside it though, funnily enough. the PV for said PVC has mounting options included in csi-driver-smb's example including <code>dir_mode=0777</code>, and <code>file_mode=0777</code>, with minor changes such as <code>uid=1001</code> and <code>gid=1001</code> I've updated them to <code>0</code>, which is the uid and gid of the root user. I've even tried updating them to <code>1000</code> which is the id of the user <code>plex</code>, but still with the same results. Anyone have any clue why I'm getting the permission denied error? 🔗 <a href="https://github.com/plexinc/pms-docker" rel="nofollow noopener" target="_blank">https://github.com/plexinc/pms-docker</a> 🔗 <a href="https://github.com/kubernetes-csi/csi-driver-smb" rel="nofollow noopener" target="_blank">https://github.com/kubernetes-csi/csi-driver-smb</a> ▶️ <a href="https://youtu.be/3S5oeB2qhyg" rel="nofollow noopener" target="_blank">https://youtu.be/3S5oeB2qhyg</a>

Recent searches

Search options

Administered by:

Server stats:

#csidriversmb