Etcd Usage Survey 2023

Please Help Us Figure Out Etcd Usage

This survey will help the Etcd maintainers prioritize work and figure out strategic direction for the project, particularly around support for uses outside of Kubernetes. With the recent discussions around merging with the Kubernetes project, and potentially removing the v3 REST endpoints, we need to get a clear picture of how people are using Etcd. Your response, with as much detail as you can provide, will help.

The detailed answers to this survey will be seen only by Etcd maintainers and the CNCF staff. Aggregated response summaries, and non-identifying quotes from essay responses, will be shared publicly with the Etcd community. To ask further questions about this survey, or to have your data removed from it, contact jberkus@redhat.com or projects@cncf.io.

Question Title

* 1. What is Your Relationship with the Etcd Project? Please check all that describe you

Contributor

Etcd End User staff

Employee of a vendor product or service that uses Etcd

Hobby/experimental user

Using Etcd for academic projects

None of the above

Question Title

* 2. How do you use Etcd? Please check all that apply

As a part of Kubernetes

To support other applications not on Kubernetes

To support other applications running in Kubernetes

In development

In production

Question Title

* 3. Non-Kubernetes Usage: If you use Etcd for any non-Kubernetes use case, how important is that usage to you? Please check all that applicable uses

Experimental/development

One of several options

Key dependency of a commercial product or service

End-user of an application that requires it

We only use Etcd as part of Kubernetes

Question Title

* 4. REST Interface: There has been discussion about dropping support for the REST API for Etcd (the endpoints under the /v3/* path), and only supporting gRPC. Are you using the v3 RESTful interface?

Yes

I'm not sure

Question Title

* 5. Description of Usage: Please describe the main ways in which you use Etcd.

Question Title

* 6. Features: What features of Etcd make it indispensable for your use-case? Please check all that apply.

It’s the official data store for Kubernetes

Distributed locking

Leader election

High availability

Transaction support

Strong consistency

Simplicity

Efficient watch

Other (please specify)

Question Title

* 7. Limitations: What current limitations prevent you from growing your non-Kubernetes usage of Etcd? Please check all that apply.

8 GB default database size limit

Limited to key value store (no custom index, no schema, no custom selectors),

Lack of multi-tenancy features

Performance and server overhead

Recent data integrity bugs

No limitations affect me

Other (please specify)

Question Title

* 8. Contact Info: If you are willing to be contacted to follow-up on your answers above, please enter your email address:

Question Title

* 9. Other Comments: Please add any other comments you have about Etcd or this survey here:

Thanks for filling out our usage survey!

Are you interested in participating in the Etcd community, and maybe contributing to Etcd? You can join us on the mailing list, at monthly video meetings, and of course on Github.

If you're already part of the Etcd community, consider getting started with contributions to the project. As a free and open source project, we're always looking for new contributors.