Coincidentally so are the t3 / t3a instances on AWS that everyone loves to use especially for dev/staging environments
Not necessarily obvious failures, but subtle errors, memory problems (like this case without an ECC capable CPU) and little instabilities.
With cloud instances I can migrate to a new instance with a couple clicks if I want.
Trying to save a couple hundred euros per month on hosting costs needs to be balanced against the risks and extra developer time.
For personal projects these old instances can be an excellent deal though.
But then I remembered that what AWS gives you is the same generation of CPU, just obfuscated.
GCP Also obfuscates it, but not as much: https://docs.cloud.google.com/compute/docs/general-purpose-m...
(note: skylake is 10 years old)
6700 should be DDR4 unless they're using some weird-ass setup.
Also, if you don't want to provision software systems, you probably shouldn't use Kubernetes at all. Both this and compute are niche businesses and neither would rent a budget server anyway.
That CPU is ancient, though. Over a decade old. That DRAM is 2-channel DDR3.
This could be a good deal for someone, but entrusting your startup’s operations to a 10 year old slow computer in Germany instead of using EKS would be an extremely short sighted move. A startup should be developing software and shipping it quickly to validate the market, not pinching pennies to save the equivalent of a couple hours of developer salary.