Are there any limitations on kubernete orchestration?


Kubernetes allow us to orchestrate nodes in clusters with hundreds of advanced features, right? Are there any limitations/restrictions on DigitalOcean kubernetes clusters if I use my own configuration / orchestration files? That is, can I program ANY feature of the kubernetes documentation in my DigitalOcean cluster, or are there any limits to DigitalOcean IaaS that prevent me from using all the features available in kubernetes?

Thank you!


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there,

DOKS is a managed offering. Because of this the configuration of the master as well as the configuration of the nodes are currently not modifiable by our customers. So if your workload requires a certain feature-flag to be enabled on the kubelet or the master api then you may not be able achieve that feature on our platform. We are frequently evaluating our customer needs for feature flags and configurations to make it into the default builds.

In general you have cluster admin access to the cluster and we do not limit the cluster admin capabilities at all.


John Kwiatkoski Senior Developer Support Engineer

Yes, DigitalOcean will have support for each feature as noted in the Kubernetes documentation. Furthermore, please see the following link for additional information regards Kubernetes on DigitalOcean:

Think different and code well,