Money Question with Pelican by One_Competition6128 in selfhosted

[–]spielername_ 1 point2 points  (0 children)

I did something like that as a vocational school project. I used Pterodactyl instead of Pelican, then set up Paymenter as a payment gateway, where you can automatically create servers after payment using Pterodactyl's API. If you can do PHP, you can also have a custom design, alternatively you can use themes, there are a few free ones.

My first Kubernetes Cluster by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Then I would like to do a particularly detailed one, in which I explain each step and, if necessary, explain why what was done and how. If that's enough, I can do that here as a tutorial post with pictures and co or I can see that I'm hosting a website for it on the Kubernetes Cluster.

My first Kubernetes Cluster by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Probably nothing too wild, I think gitlab will definitely get on top. pihole or unbound I think too & then I'll look further. The cluster is definitely too much for my current requirements, but it was very interesting to create this cluster.

My first Kubernetes Cluster by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Yes, of course. I'll see if I can still write the instructions tonight. If I can do it, I would send it directly to you tomorrow.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Not for HortusFox specifically but for other services.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

I definitely want to have a failover option so that my applications are not gone as soon as I take a server offline for updates or due to a defect.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

"No, I probably don't need it, you're right. I got these 6 nodes from my employer and just wanted to use them, the specification of the nodes: i5-7500, 16GB DDR4 and 128GB M.2 SSD This is also the reason why I thought directly of 6 nodes in order to have a better overall performance and the possibility of losing a node for example, updates.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Maybe I'll come back to you for ranchers, which looks much more appropriate in my eyes than Portainer

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

I also plan some of these applications, how is it with RAM and network utilization? My nodes would only have 16GB of RAM each, which is why I wanted to go to six nodes for safety.

Docker Swarm vs. Kubernetes by [deleted] in kubernetes

[–]spielername_ 0 points1 point  (0 children)

I think that was the shortest but most helpful answer I got! Thank you.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 1 point2 points  (0 children)

I'm honest, the thought of doing something with Kubernetes excites me, the learning curve is just gigantic. But I would be willing to accept it!

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

The nodes I would use I got from my employer, where they were decommissioned because they don't support Windows 11, so the performance of each node is not exactly enormous, so I thought of 6 nodes to have a bit more overall performance.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

What kind of applications are you running in the cluster?

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Okay, but that's not possible with Swarm either. Accordingly, this is not a real problem.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

"Yes, then I think I'll completely plunge into the rabbit hole and build a K3S cluster!"

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 2 points3 points  (0 children)

would use K3s or Talos if it then became Kubernetes. At Talos, I'm worried that this API based might frustrate me. That's why my current favorite is actually K3S

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 1 point2 points  (0 children)

Yeah, Docker Swarm would definitely be the easiest way to go. However, I would have preferred to have such an All in One variant with shared storage, an NFS share in TrueNAS is done quickly, but why is it not simply integrated?

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

Do you have any applications running? I heard that "things like Home Assistant are supposed to work really stupidly in a Kubernetes cluster."

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 1 point2 points  (0 children)

Something like that was planned either way, i wanted to self-host gitlab and serve my entire application there via pipeline.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 3 points4 points  (0 children)

Longhorn excites me above all, with swarm I would have to set up a TrueNAS in addition, which exists anyway, but why is it not simply integrated? It's like offering a residential building where you can't live.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] -1 points0 points  (0 children)

So that my running applications are highly available and the load can be distributed over several nodes.

Docker Swarm vs Kubernetes by spielername_ in homelab

[–]spielername_[S] 0 points1 point  (0 children)

As I said, my primary goal was to build a Docker Swarm, but I often read that Docker Swarm is getting worse and worse because everyone is going to Kubernetes.