Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I wanted to try DOKS due to the competitive and transparent pricing model. DOKS ships with Cilium enabled as the default CNI. Cilium is awesome, however I noticed the DOKS-enabled Cilium offering is not very configurable nor flexible from a user perspective. In other clusters (a mix of both self-managed and managed), I am using a custom-installed Cilium with certain features enabled, for example:
kube-proxy (i.e. removal of kube-proxy)Does anyone have any patterns for safely configuring Cilium on DOKS, or should I look elsewhere for a managed Kubernetes offering? My proposition is allowing the DOKS bootstrapping to be more configurable, such as having an advanced option of not enabling a CNI at all so that it is up to the user for those that want to configure their own (Cilium, Calico, …).
This is possible on AWS EKS, Azure AKS, and GCP GKE, so would be a huge value prop for DigitalOcean imo.
jazzybruno
jazzybruno
9c24208528c843f2bcdb7d54782c69
Sean DesPortes
Robin van der Knaap
Robin van der Knaap
Attila Kovacs
Tomy Hsieh
Tuschl
Alexander Freyr
marcelhaldimann
Emiliano Maccaferri