Hacker News new | past | comments | ask | show | jobs | submit login

Kubernetes + Cluster API. This unlocks the ability to use one or multiple providers: https://cluster-api.sigs.k8s.io/reference/providers.html

* Alibaba Cloud

* AWS

* Azure

* Azure Stack HCI

* Baidu Cloud

* BYOH

* Metal3

* DigitalOcean

* Exoscale

* GCP

* Hetzner

* IBM Cloud

* KubeVirt

* MAAS

* Nested

* Nutanix

* OpenStack

* Equinix Metal (formerly Packet)

* Sidero

* Tencent Cloud

* vSphere




Also Oracle OCI has OKE, which is Oracle Kubernetes Engine. It works nicely and the quality of service has been very good in my experience over the past four years.

Disclaimer: I currently work at Oracle.


Can you find anyone who doesn't work at Oracle that can back up this bold assertion?


I’m sure that can be put into some company’s next Oracle licensing true up.


Why is it a bold assertion? Looks like the Oracle folks just need to submit a PR to the CAPI docs to include a link to their provider which is available now.

https://github.com/oracle/cluster-api-provider-oci


It's usually quite hard to find people who don't work at Oracle who speak positively about Oracle Cloud.

We tried to use it at work, it was the second-biggest disaster of a cloud provider we've ever encountered (Huawei is the first). Stuff is just broken so often it's hard to ever feel like you can trust it.


Literally anything that puts oracle cloud in a positive light is a bold assertion.


This sounds like a nifty solution for compute, but I suppose for data storage and such you would want a separate managed service? Or does this hook into that for various providers too?


Storage is already abstracted via Kubernetes with persistent volume claims and CSI (container storage interface)

You can specify the default storage class to use the provider's CSI driver. The PVC is then specified and consumed the same way in a portable manner across providers.


With "storage" I'm thinking something more powerful beyond plain files, e.g. relational databases.


Block storage? When you create your persistent volume claim, you can specify an accessMode. "readWriteOnce" will target block storage of the storageClass, "readWriteMany" will use file.

You can also choose something specific like a mounted hostVolume which is not provider specifc.

Cutting edge stuff like NVMe-oF is even possible, the CSI ecosystem is very active. https://github.com/spdk/spdk-csi


We run almost all of our production databases on k8s - postgres, clickhouse, cockroachdb and more. Many others do too. K8s itself already comes with a db of sorts - etcd so it’s not a non-standard usecase.


planetscale (if I need rdbms) or firestore or dynamodb (if I need just document). I checked latency of planetscale and dynamodb from frankfurt,paris,singapore from DO/linode/scaleway to db in same region; these are low latency (mostly single digit).

For single server, I'd just use sqlite.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: