#k3s — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #k3s, aggregated by home.social.
-
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.
-
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.
-
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.
-
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.
-
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.
-
K3sup – bootstrap K3s over SSH in < 60s
https://github.com/alexellis/k3sup
#HackerNews #K3sup #K3s #SSH #bootstrap #DevOps #Kubernetes #OpenSource
-
K3sup – bootstrap K3s over SSH in < 60s
https://github.com/alexellis/k3sup
#HackerNews #K3sup #K3s #SSH #bootstrap #DevOps #Kubernetes #OpenSource
-
K3sup – bootstrap K3s over SSH in < 60s
https://github.com/alexellis/k3sup
#HackerNews #K3sup #K3s #SSH #bootstrap #DevOps #Kubernetes #OpenSource
-
K3sup – bootstrap K3s over SSH in < 60s
https://github.com/alexellis/k3sup
#HackerNews #K3sup #K3s #SSH #bootstrap #DevOps #Kubernetes #OpenSource
-
K3sup – bootstrap K3s over SSH in < 60s
https://github.com/alexellis/k3sup
#HackerNews #K3sup #K3s #SSH #bootstrap #DevOps #Kubernetes #OpenSource
-
Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s
-
Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s
-
Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s
-
Guess which node is currently hanging by its network cable outside the rack. #homelab #raspberrypi #k3s
-
/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.
-
/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.
-
/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.
-
#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.
https://www.storagereview.com/news/suse-unveils-ai-factory-with-nvidia-highlights-enterprise-sovereignty-gap #AI #SovereignAI -
#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.
https://www.storagereview.com/news/suse-unveils-ai-factory-with-nvidia-highlights-enterprise-sovereignty-gap #AI #SovereignAI -
#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.
https://www.storagereview.com/news/suse-unveils-ai-factory-with-nvidia-highlights-enterprise-sovereignty-gap #AI #SovereignAI -
#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.
https://www.storagereview.com/news/suse-unveils-ai-factory-with-nvidia-highlights-enterprise-sovereignty-gap #AI #SovereignAI -
#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.
https://www.storagereview.com/news/suse-unveils-ai-factory-with-nvidia-highlights-enterprise-sovereignty-gap #AI #SovereignAI -
Found this nice tui for kubernetes this weekend - https://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
-
Found this nice tui for kubernetes this weekend - https://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
-
Found this nice tui for kubernetes this weekend - https://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
-
Found this nice tui for kubernetes this weekend - https://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
-
Found this nice tui for kubernetes this weekend - https://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
-
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.
-
@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.
-
@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.
-
@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.
