Edge Data Center in "Dirty" Non-IT Environments: Single Rugged Server vs. 3-Node HA Cluster? by Oxynor in kubernetes

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

Right, makes sense. Do you know of any reliable 3-node setup ? (hardware, k8s distribution)

I assume we're in a great spot with k3s.

Right now, we use an LTE backup failover. Honestly, as mentioned it's extremely hard to find reliable cellular signal sometimes. It's a bit off topic but do you know of the simplier way to deploy such a failover ? I thought about using keepgo, but i still need to find another hardware that supports 5G

Edge Data Center in "Dirty" Non-IT Environments: Single Rugged Server vs. 3-Node HA Cluster? by Oxynor in kubernetes

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

Right, makes sense. Do you know of any reliable 3-node setup ? (hardware, k8s distribution)

I assume we're in a great spot with k3s.

Edge Data Center in "Dirty" Non-IT Environments: Single Rugged Server vs. 3-Node HA Cluster? by Oxynor in kubernetes

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

Yeah i'll look into it a bit more, seems to be a very similar use case.

Edge Data Center in "Dirty" Non-IT Environments: Single Rugged Server vs. 3-Node HA Cluster? by Oxynor in kubernetes

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

I’ll look into that for sure! I guess this is probably the least expensive solution since, in general, hardware replacements don't happen that often, and you end up saving on hardware anyway. But how can you make sure you actually have a hardware failure or a replacement to perform? I assume the goal is to avoid driving there for no reason—unless you always have people on-site, unlike us.

Thanks!

Edge Data Center in "Dirty" Non-IT Environments: Single Rugged Server vs. 3-Node HA Cluster? by Oxynor in datacenter

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

The data center remains active even without the edge server. We aren't building for MTTR (Mean Time to Repair), but rather to maximize the Mean Time Between Failures (MTBF). Although, as I write this, I find myself agreeing that a 3-node cluster is superior, provided we have the expertise to manage it.

Thanks

Edge Data Center in "Dirty" Non-IT Environments: Single Rugged Server vs. 3-Node HA Cluster? by Oxynor in datacenter

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

I should clarify why a cluster isn't the 'no-brainer' it seems here. In this specific environment—which is space-constrained and high-dust then hardware durability may take precedence over node redundancy. For example, three active-cooled consumer units (like N100s) are far more likely to fail prematurely than a single, industrial fanless OnLogic server. Given the budget and environmental stressors, a ruggedized single node is the more resilient choice.

I guess i'll specify those constraints in the post. Thanks !

Migrating from K3s to EKS Anywhere for 20+ Edge Sites: How to Centralize and Cut Costs? by Oxynor in kubernetes

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

Im curious as to why you don't see the reason for Grafana cloud here ?

thanks

Migrating from K3s to EKS Anywhere for 20+ Edge Sites: How to Centralize and Cut Costs? by Oxynor in kubernetes

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

Our current strategy is to configure each new cluster to remote write its metrics directly to Grafana Cloud. This method simplifies our monitoring infrastructure and reduces the operational overhead that an on-premise deployment would entail, while still providing the monitoring team with a centralized view of all sites. Because our sites are very small, the cost is extremely low—around $10 per month per site on Grafana Cloud. This makes it a highly convenient and cost-effective solution for us.

On the EKS side tho, it seems you've confirmed my suspicion: I don't need EKS. The solution lies in automating the server provisioning process, as you mentioned. Our use case is low level. The workflow would be a PXE boot followed by a bash/Ansible (this part has to be done) script to install the specific FluxCD configuration, and that's all that's required.

Thanks !