In etcd used in Kubernetes, what is the significance of the 1.5MB size limit for an individual value stored in etcd?

• A. Default size for a backup snapshot
• B. Maximum size for a single etcd cluster
• C. Recommended maximum size for an individual value stored in etcd
• D. Typical size of a key in etcd

Answer: (C)

The main idea is that keeping an individual value small helps keep etcd fast and resource-friendly. In etcd, every write is replicated to all members and stored in raft logs and snapshots. A large value makes those logs and snapshots bigger, which increases memory usage, I/O, and the time needed for replication and compaction. The 1.5 MB figure is a practical guideline for the maximum size of a single value stored in etcd to maintain good performance and stability. If you need to store larger data, placing it outside etcd and storing a reference (pointer) in etcd is the recommended approach.