DOKS node's persistent disk.

I’m currently building an application using the DOKS. I have a question regarding Persistance Volumes and node’s disks and cluster upgrades. The nodes is obviously a droplet instances that has persistent disks.

The questions:

  1. Can I utilize the node’s disk for my Persistence Volume with something for example Longhorn for Kubernetes Storage?
  2. How do DigitalOcean handle upgrades? Do the nodes in the cluster recreated?
  3. Will my data on the node’s disk gone after upgrades (manually or automatically)

I mean you had nodes with 160GB+ of disk. If I can’t utilize it because the data would be gone because the nodes are recreated on upgrades that’s a bummer.

Submit an answer

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.

Bobby Iliev
Site Moderator
Site Moderator badge
January 2, 2024

Hi there,

As far as I can tell, it appears that using Longhorn with DOKS might not be feasible due to specific compatibility issues as discussed in this Longhorn GitHub issue.

Given the challenges with using Longhorn in DOKS, here’s an overview of some alternatives, including running Rook/Ceph on DOKS, which might suit your needs better.

DigitalOcean Spaces for Object Storage

  • Use Cases: Ideal for storing and serving large amounts of unstructured data like images, videos, backups, etc. Spaces is an S3-compatible service, scalable and secure for such requirements:

DigitalOcean Block Storage

  • Capabilities: Offers robust, high-performance storage but with a limitation - a Block Storage volume can be mounted to only one node at a time.
  • Ideal Scenarios: Best suited for databases or single-node applications needing reliable, persistent storage.

Running Rook/Ceph on DOKS

  • Overview: For scenarios requiring shared storage accessible across multiple nodes, running Rook/Ceph on DOKS can be an effective solution.
  • Rook/Ceph: It is an open-source storage platform that provides scalable and redundant storage using commodity hardware, and it’s well-suited for Kubernetes environments.
  • DigitalOcean’s Storage Offering: Here is a great article by Jack Pearce, that covers the whole setup process and describes the block storage limitation.
  • Rook/Ceph Advantage: By deploying Rook with Ceph within your DOKS environment, you can create a more flexible storage solution that allows pods across different nodes to share storage, overcoming the single-node limitation of standard block storage.

If you have further questions or need more detailed advice, the community is here to help!



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel