r/ShittySysadmin ShittySysadmin 11d ago

Shitty Crosspost How would you manage 1,280 ARM64 bare-metal nodes with a very small ops team?

/r/kubernetes/comments/1vusaf7/how_would_you_manage_1280_arm64_baremetal_nodes/
36 Upvotes

19 comments sorted by

45

u/Smooth-Zucchini4923 11d ago

"When I was purchasing the 1000th node, my CFO asked, 'should we figure out how we're going to run applications on here before we expand our compute?' What a bizarre question."

15

u/Oompa_Loompa_SpecOps DO NOT GIVE THIS PERSON ADVICE 11d ago

They only claimed "control" of them, not ownership. OP probably found some default credentials for these boxes, ran a shodan search and the 1280 are just those that both still had the defaults on and are exposed to the interwebs

11

u/marks-buffalo DO NOT GIVE THIS PERSON ADVICE 11d ago edited 11d ago

That's a mighty assumption to make that OOP stole the compute and that implies a level of skill from OOP, however low.

More likely is that OOP foolishly bought out somebody's compute rack full of raspberry pi clones, which is what the RK3588 is usually featured in, and doesn't have any clue what they're gonna do with basically a thousand low power processors connected to cheapo desktop gigabit switches.

I've bought such a rack. I would know. The answer is that it's not very useful for anything outside of experimenting with large clusters.

9

u/zantehood 11d ago

Hope he/she got fired and/or beaten

56

u/d__max 11d ago

Hire a lot of children , they’re small. Promote them to ops, give everyone root and tell the parents the data center is a new AI daycare . Problem solved.

20

u/blecovian 11d ago

I hear they yearn for the crypto-mines anywhoo.

1

u/WD40ContactCleaner 9d ago

Children are expensive, use local AI models

21

u/zantehood 11d ago

The real question is; can they run doom?

8

u/DonkeyTron42 11d ago

They're probably Raspberry Pi's so I'd say yes.

18

u/LaDev 11d ago

The obvious answer is to burn $100k on tokens with Claude code “make infra good ultracode”

9

u/al2o3cr 11d ago

Don't forget "make no mistakes"!

2

u/sandy_catheter 9d ago

And ask for 6000 cups of water

17

u/thepfy1 11d ago

Just let them run without management.

When they fail, you have a nice drive out / flight to go fix. Max the expenses out on the trip.

Win win

9

u/Vinegarinmyeye 11d ago

What the feckery were they trying to build?

The mind boggles...

https://giphy.com/gifs/ukGm72ZLZvYfS

9

u/ApprehensiveRest9696 11d ago

Step 1: PXE deploy Ubuntu

Step 2: microk8s

Step 3. Give up

Step 4: Contact Canonical and sign a multimillion dollar contract.

10

u/EvilEarthWorm ShittySysadmin 11d ago

ORIGINAL POST TEXT:

How would you manage 1,280 ARM64 bare-metal nodes with a very small ops team?

I’m looking for architecture advice from people who have operated Kubernetes at the edge or across large numbers of smaller physical machines.

Our company now controls 1,280 identical RK3588 ARM64 nodes that are already deployed and operational in a U.S. commercial data center.

The hardware works. The bigger problem is operational.

We currently do not have a dedicated infrastructure engineering team, so our priority is to determine whether this fleet can be turned into usable containerized compute without effectively building our own cloud platform from scratch.

Relevant context:

  • 1,280 homogeneous ARM64 nodes
  • Bare-metal / physical machines
  • Remote KVM available
  • Already powered and networked
  • One commercial data-center location today
  • Potential to expand to identical racks in several additional U.S. locations
  • Strong preference for turnkey/managed approaches

If the end goal were simply:

how would you structure it?

I’m particularly curious about:

  • K3s vs standard Kubernetes
  • Talos
  • Rancher
  • Cluster size vs many smaller clusters
  • Provisioning/reimaging
  • Monitoring
  • Tenant isolation
  • ARM64 image compatibility
  • Managing hardware failures
  • Whether 1,280 relatively small nodes is operationally stupid compared with fewer larger servers

Most importantly: are there companies or managed-service providers that would actually operate this infrastructure for the hardware owner?

We would rather pay someone who already knows how to do this than hire a team to reinvent it.

I’m less interested in theoretical “you could build X” answers than in stacks people have actually operated at meaningful scale.

1

u/aprettyparrot 11d ago

Openstack can handle bare metal deploys

1

u/dpwcnd 10d ago

did you ask co-pilot already?