home.social

#k3s — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #k3s, aggregated by home.social.

  1. 病假给了我很多时间去搞homelab 今天把terraform module 加上了, ansible playbook也跑起来了,这边 tofu apply 然后 ansible-playbook 进行config. 还把tasks 整合进了 roles. 今天还读了一点production kubernetes 觉得受益匪浅! 非常棒的一本书!

    病假后半段我状态好点了不再一整天都虚弱躺着了就开始不停思考, 我感觉自己把整个人生都分析和重构了一遍, 从财务规划到退休计划从职业发展到知识管理…

    明天打算把这两步整合一下:provision a VM, install k3s, install Rancher, then let Rancher create/register another downstream cluster 顺便处理下cert-manager DNS-01 拿证书

    #homelab #ansible #opentofu #k3s #rancher #certmanager

  2. 病假给了我很多时间去搞homelab 今天把terraform module 加上了, ansible playbook也跑起来了,这边 tofu apply 然后 ansible-playbook 进行config. 还把tasks 整合进了 roles. 今天还读了一点production kubernetes 觉得受益匪浅! 非常棒的一本书!

    病假后半段我状态好点了不再一整天都虚弱躺着了就开始不停思考, 我感觉自己把整个人生都分析和重构了一遍, 从财务规划到退休计划从职业发展到知识管理…

    明天打算把这两步整合一下:provision a VM, install k3s, install Rancher, then let Rancher create/register another downstream cluster 顺便处理下cert-manager DNS-01 拿证书

    #homelab #ansible #opentofu #k3s #rancher #certmanager

  3. I'm making progress on my local #LLM experiments. Now we moved from single node to 2 node Kubernetes, here a blog post about my initial setup with a bunch of new Bench-marking results: blog.t1m.me/blog/building-own-

    Currently using a simple #k3s server / agent set-up, with DNS-1 certificate issuing and everything in a private #tailscale network.

    Already taking the next steps towards migrating from #ollama to #vLLM and optimizing prompt / model caching + routing. Several more changes coming up :)

  4. I'm making progress on my local #LLM experiments. Now we moved from single node to 2 node Kubernetes, here a blog post about my initial setup with a bunch of new Bench-marking results: blog.t1m.me/blog/building-own-

    Currently using a simple #k3s server / agent set-up, with DNS-1 certificate issuing and everything in a private #tailscale network.

    Already taking the next steps towards migrating from #ollama to #vLLM and optimizing prompt / model caching + routing. Several more changes coming up :)

  5. I'm making progress on my local #LLM experiments. Now we moved from single node to 2 node Kubernetes, here a blog post about my initial setup with a bunch of new Bench-marking results: blog.t1m.me/blog/building-own-

    Currently using a simple #k3s server / agent set-up, with DNS-1 certificate issuing and everything in a private #tailscale network.

    Already taking the next steps towards migrating from #ollama to #vLLM and optimizing prompt / model caching + routing. Several more changes coming up :)

  6. I'm making progress on my local #LLM experiments. Now we moved from single node to 2 node Kubernetes, here a blog post about my initial setup with a bunch of new Bench-marking results: blog.t1m.me/blog/building-own-

    Currently using a simple #k3s server / agent set-up, with DNS-1 certificate issuing and everything in a private #tailscale network.

    Already taking the next steps towards migrating from #ollama to #vLLM and optimizing prompt / model caching + routing. Several more changes coming up :)

  7. I'm making progress on my local #LLM experiments. Now we moved from single node to 2 node Kubernetes, here a blog post about my initial setup with a bunch of new Bench-marking results: blog.t1m.me/blog/building-own-

    Currently using a simple #k3s server / agent set-up, with DNS-1 certificate issuing and everything in a private #tailscale network.

    Already taking the next steps towards migrating from #ollama to #vLLM and optimizing prompt / model caching + routing. Several more changes coming up :)

  8. Wow that was a long break, I've got very little time to talk here lately, work and life taking over...

    But damn was there some activity on the k3s cluster 😅

    Stalwart is finally up and running, with all of my domain names
    I've tested what happens when the server is down (because outages do happen) and everything was delivered as expected

    And using SMTP2Go to avoid having to maintain an IP reputation

    Chef's kiss

    #cluster #k3s #k8s #stalwart #mail #smtp #smtp2go #break #pause

  9. Wow that was a long break, I've got very little time to talk here lately, work and life taking over...

    But damn was there some activity on the k3s cluster 😅

    Stalwart is finally up and running, with all of my domain names
    I've tested what happens when the server is down (because outages do happen) and everything was delivered as expected

    And using SMTP2Go to avoid having to maintain an IP reputation

    Chef's kiss

    #cluster #k3s #k8s #stalwart #mail #smtp #smtp2go #break #pause

  10. Wow that was a long break, I've got very little time to talk here lately, work and life taking over...

    But damn was there some activity on the k3s cluster 😅

    Stalwart is finally up and running, with all of my domain names
    I've tested what happens when the server is down (because outages do happen) and everything was delivered as expected

    And using SMTP2Go to avoid having to maintain an IP reputation

    Chef's kiss

    #cluster #k3s #k8s #stalwart #mail #smtp #smtp2go #break #pause

  11. Wow that was a long break, I've got very little time to talk here lately, work and life taking over...

    But damn was there some activity on the k3s cluster 😅

    Stalwart is finally up and running, with all of my domain names
    I've tested what happens when the server is down (because outages do happen) and everything was delivered as expected

    And using SMTP2Go to avoid having to maintain an IP reputation

    Chef's kiss

    #cluster #k3s #k8s #stalwart #mail #smtp #smtp2go #break #pause

  12. Which Linux #Distro are people using these days to run #K3s on modest/old machines?

    I have an old notebook
    with an Intel Core i5-6200U 2.3/2.8GHz dual core, 8GB RAM, 256GB SSD
    and 2 external 2TB HDD

    And I wish for it to run a few self-written small binaries, maybe a file server and home assistant

  13. Which Linux #Distro are people using these days to run #K3s on modest/old machines?

    I have an old notebook
    with an Intel Core i5-6200U 2.3/2.8GHz dual core, 8GB RAM, 256GB SSD
    and 2 external 2TB HDD

    And I wish for it to run a few self-written small binaries, maybe a file server and home assistant

  14. Which Linux #Distro are people using these days to run #K3s on modest/old machines?

    I have an old notebook
    with an Intel Core i5-6200U 2.3/2.8GHz dual core, 8GB RAM, 256GB SSD
    and 2 external 2TB HDD

    And I wish for it to run a few self-written small binaries, maybe a file server and home assistant

  15. Which Linux #Distro are people using these days to run #K3s on modest/old machines?

    I have an old notebook
    with an Intel Core i5-6200U 2.3/2.8GHz dual core, 8GB RAM, 256GB SSD
    and 2 external 2TB HDD

    And I wish for it to run a few self-written small binaries, maybe a file server and home assistant

  16. Which Linux #Distro are people using these days to run #K3s on modest/old machines?

    I have an old notebook
    with an Intel Core i5-6200U 2.3/2.8GHz dual core, 8GB RAM, 256GB SSD
    and 2 external 2TB HDD

    And I wish for it to run a few self-written small binaries, maybe a file server and home assistant

  17. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  18. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  19. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  20. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  21. Rebuilding my #homelab once more. I switched from #k3s to #talos quite a while ago. As it goes, my experiments left k8s in a ... well ... undefined state. Time to set it up all over again. Sending a huge thanks to Jochen from a few months ago for automating everything. #Talos + #Ansible + #Argo make for really nice experience and I got all my services back in no time, including data.

  22. Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s

  23. Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s

  24. Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s

  25. Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s

  26. /me just deployed gotosocial on k3s. what it makes special because the server only has 1 gb ram, 1 cpu, 10 gb ssd, and 1.5 gb swap.

    #k3s #gotosocial #selfhosting #kubernetes

  27. /me just deployed gotosocial on k3s. what it makes special because the server only has 1 gb ram, 1 cpu, 10 gb ssd, and 1.5 gb swap.

    #k3s #gotosocial #selfhosting #kubernetes

  28. /me just deployed gotosocial on k3s. what it makes special because the server only has 1 gb ram, 1 cpu, 10 gb ssd, and 1.5 gb swap.

    #k3s #gotosocial #selfhosting #kubernetes

  29. #SUSE Unveils #AIFactory with #NVIDIA, Highlights Enterprise Sovereignty Gap
    The stack integrates several NVIDIA components, including NIM microservices, open Nemotron models, NeMo for #AIagent development and management, Run:ai for GPU orchestration, NVIDIA Kubernetes Operators, OpenShell for secure agent runtime support, and NemoClaw, which uses SUSE #K3s as part of a reference architecture for more secure autonomous agent deployments.
    storagereview.com/news/suse-un #AI #SovereignAI

  30. #SUSE Unveils #AIFactory with #NVIDIA, Highlights Enterprise Sovereignty Gap
    The stack integrates several NVIDIA components, including NIM microservices, open Nemotron models, NeMo for #AIagent development and management, Run:ai for GPU orchestration, NVIDIA Kubernetes Operators, OpenShell for secure agent runtime support, and NemoClaw, which uses SUSE #K3s as part of a reference architecture for more secure autonomous agent deployments.
    storagereview.com/news/suse-un #AI #SovereignAI

  31. Unveils with , Highlights Enterprise Sovereignty Gap
    The stack integrates several NVIDIA components, including NIM microservices, open Nemotron models, NeMo for development and management, Run:ai for GPU orchestration, NVIDIA Kubernetes Operators, OpenShell for secure agent runtime support, and NemoClaw, which uses SUSE as part of a reference architecture for more secure autonomous agent deployments.
    storagereview.com/news/suse-un

  32. #SUSE Unveils #AIFactory with #NVIDIA, Highlights Enterprise Sovereignty Gap
    The stack integrates several NVIDIA components, including NIM microservices, open Nemotron models, NeMo for #AIagent development and management, Run:ai for GPU orchestration, NVIDIA Kubernetes Operators, OpenShell for secure agent runtime support, and NemoClaw, which uses SUSE #K3s as part of a reference architecture for more secure autonomous agent deployments.
    storagereview.com/news/suse-un #AI #SovereignAI

  33. #SUSE Unveils #AIFactory with #NVIDIA, Highlights Enterprise Sovereignty Gap
    The stack integrates several NVIDIA components, including NIM microservices, open Nemotron models, NeMo for #AIagent development and management, Run:ai for GPU orchestration, NVIDIA Kubernetes Operators, OpenShell for secure agent runtime support, and NemoClaw, which uses SUSE #K3s as part of a reference architecture for more secure autonomous agent deployments.
    storagereview.com/news/suse-un #AI #SovereignAI

  34. Found this nice tui for kubernetes this weekend - github.com/janosmiko/lfk

    One of the things I like about it is that it has #argocd specific logic - you can use it to alter argo settings and do other things you might otherwise do with the argocd command line tool

    Looks pretty neat, especially for #homelab @homelab #k8s users

    #sre #devops #k8s #kubernetes #k3s #talos

  35. Found this nice tui for kubernetes this weekend - github.com/janosmiko/lfk

    One of the things I like about it is that it has #argocd specific logic - you can use it to alter argo settings and do other things you might otherwise do with the argocd command line tool

    Looks pretty neat, especially for #homelab @homelab #k8s users

    #sre #devops #k8s #kubernetes #k3s #talos

  36. Found this nice tui for kubernetes this weekend - github.com/janosmiko/lfk

    One of the things I like about it is that it has specific logic - you can use it to alter argo settings and do other things you might otherwise do with the argocd command line tool

    Looks pretty neat, especially for @homelab users