Selective Analogy of Mechanisms and Tools in Kubernetes Lifecycle for Disaster Recovery

Sameer,; De, Suman; Singh, R Prashant

doi:10.1109/icmnwc56175.2022.10031926

Search citation statements

Order By: Relevance

Paper Sections

Select...

Cri-o and Kubernetes As A Container Orchestrator1

Citation Types

Supporting

Mentioning

Contrasting

Year Published

2023

2024

Publication Types

Select...

Article1

Other1

Relationship

Self Cite0

Independent2

Authors

Journals

Cited by 2 publications

(1 citation statement)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Self-healing attempts to restart failed containers automatically. The load balance ensures a fair load distribution among the nodes in the cluster [39,41].…”

Section: Cri-o and Kubernetes As A Container Orchestratormentioning

confidence: 99%

A Comparative Analysis of High Availability for Linux Container Infrastructures

Šimon,

Huraj,

Búčik

2023

Future Internet

View full text Add to dashboard Cite

In the current era of prevailing information technology, the requirement for high availability and reliability of various types of services is critical. This paper focusses on the comparison and analysis of different high-availability solutions for Linux container environments. The objective was to identify the strengths and weaknesses of each solution and to determine the optimal container approach for common use cases. Through a series of structured experiments, basic performance metrics were collected, including average service recovery time, average transfer rate, and total number of failed calls. The container platforms tested included Docker, Kubernetes, and Proxmox. On the basis of a comprehensive evaluation, it can be concluded that Docker with Docker Swarm is generally the most effective high-availability solution for commonly used Linux containers. Nevertheless, there are specific scenarios in which Proxmox stands out, for example, when fast data transfer is a priority or when load balancing is not a critical requirement.

show abstract

“…Self-healing attempts to restart failed containers automatically. The load balance ensures a fair load distribution among the nodes in the cluster [39,41].…”

Section: Cri-o and Kubernetes As A Container Orchestratormentioning

confidence: 99%