ENHANCING ETCD OPERATIONS  IN KUBERNETES WITH LEVEL DB AND BADGER DB

Satya Tsaliki; Dr.B.PurnachandraRao

ENHANCING ETCD OPERATIONS IN KUBERNETES WITH LEVEL DB AND BADGER DB

Author(s)	Satya Tsaliki, Dr.B.PurnachandraRao
Country	United States
Abstract	Kubernetes is an orchestration tool whose tasks involve managing application container workloads, their configuration, deployments, service discovery, load balancing, scheduling, scaling, and monitoring, and many more tasks which might spread across multiple machines across many locations. Kubernetes needs to maintain coordination between all the components involved. But to achieve that reliable coordination, k8s needs a data source that can help with the information about all the components, their required configuration, state data, etc. That data store must provide a consistent, single source of truth at any given point in time. In Kubernetes, that job is done by etcd. Etcd is the data store used to create and maintain the version of the truth. Etcd is a strongly consistent, distributed key-value store that provides a reliable way to store data that needs to be accessed by a distributed system or cluster of machines. Applications of any complexity, from a simple web app to Kubernetes, can read data from and write data into etcd. A simple use case is storing database connection details or feature flags in etcd as key-value pairs. These values can be watched, allowing your app to reconfigure itself when they change. When ever we are sending apply command using kubectl or any other client API Server authenticates the request, authorizes the same, and updates to etcd on the new configuration. Etcd receives the updates (API Server sends the updated configuration to etcd), then etcd writes the updated configuration to its key-value store. Etcd replicates the updated data across its nodes and it ensures data consistency across all the nodes. It carries the cluster state by storing the latest state at key value store. In this paper we will discuss about implementation of ETCD using Ledger DB and Badger DB. Badger DB is showing high performance than ledger DB implementation. We will work on to prove that Badger DB implementation provides better CPU utilization than ledger DB implementation.
Keywords	Kubernetes (K8S), Cluster, Nodes, Deployments, Pod, configMaps, Secrets, Persistent Volume, Persistent Volume Claim, ReplicaSets, Statefulsets, Service, Service Abstraction, , Ledger DB , Badger DB. ETCD.
Field	Computer Applications
Published In	Volume 4, Issue 4, July-August 2022
Published On	2022-08-24

View / Download PDF File

E-ISSN 2582-2160

doi

CrossRef DOI is assigned to each research paper published in our journal.

IJFMR DOI prefix is
10.36948/ijfmr

Downloads

Research Paper Format Copyright Permission Form and Undertaking Form Cover Page Vol 7 Isu 2 Cover Page Vol 7 Isu 1 Cover Page Vol 6 Isu 6

All research papers published on this website are licensed under Creative Commons Attribution-ShareAlike 4.0 International License, and all rights belong to their respective authors/researchers.

CC-BY-SA

About IJFMR Fees & Payment Current Issue Publication Archive	Submit Research Paper Track Submission Status Publication Guidelines Publication Ethics Peer Review & Plagiarism	Join as a Reviewer Editors & Reviewers Reviewer Referral Program Get Reviewer Membership Certi.	Website/Journal Policies Usage Policy Content Policies Privacy Policy

Contact Us		+91-9687-828-838	editor@ijfmr.com

International Journal For Multidisciplinary Research

A Widely Indexed Open Access Peer Reviewed Multidisciplinary Bi-monthly Scholarly International Journal

ENHANCING ETCD OPERATIONS IN KUBERNETES WITH LEVEL DB AND BADGER DB

Share this