How long does it typically take a cluster to come up and be live?

I have successfully launched my app using DO Kubernetes, but have noticed that from typing kubectl apply for the first time to the cluster being able to serve requests takes around 5 minutes. Is this typical? It seems long but I am not sure what to expect.

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

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

Sign In or Sign Up to Answer

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.

John Kwiatkoski
DigitalOcean Employee
DigitalOcean Employee badge
November 14, 2019
Accepted Answer

Hi there!

Yes it can take anywhere from 3-10min for the cluster to come up. This is heavily dependent on the cluster size and how many nodes need to bootstrap as well as other factors such as the standard performance variability.

Let me know if you have any additional questions.


John Kwiatkoski Senior Developer Support Engineer

Yes, I agree with the other answers to your post. The cluster will definitely take several minutes to be up and operational. Also, kubectl apply is dependent on what you’re doing within the resource YAML.

For example, the size of your image(s) and what polices you’re using here to obtain the image. In general, this should be instant but it really depends what you’re doing in the YAML.

Think different and code well,


Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I found this great article that explains how to configure rolling updates (another place I was seeing downtime after kubectl apply