Loading article...
Loading article...
Stream/Area:
-
Subject:
-
Paper ID:
IJSREM6597
Volume:
4 |
12 |
Dec 2020
Pages:
1-6
Publication Frequency:
Monthly (12 issues per year)
License:International Journal of Scientific Research in Engineering and Management follows the Creative Commons Attribution 4.0 (CC BY 4.0) License, allowing free use and distribution with proper attribution.
Independent Researcher
Sunnyvale, CA, USA 94086
This paper presents a consolidated set of Site Reliability Engineering (SRE) strategies for achieving and sustaining high reliability on large Kubernetes platforms. Kubernetes has become the de facto control plane for containerized workloads, yet operating it reliably at scale, across thousands of nodes and mission-critical services, introduces failure modes that traditional operations practices do not address. We examine the principal reliability challenges that emerge at scale, including control plane saturation, expanding failure domains, and operational toil. We then map core SRE constructs (service level indicators and objectives, error budgets, and blameless incident response) onto the Kubernetes operating model, and describe concrete architectural patterns for high availability such as control plane redundancy, topology aware workload distribution, and multi cluster topologies. We further discuss observability, capacity management and autoscaling, resilience engineering through chaos testing, and progressive delivery. The strategies are synthesized into actionable guidance for platform teams responsible for mission-critical cloud services, and we conclude with open challenges in automating reliability for increasingly heterogeneous, multi-tenant environments.
KEYWORDS
Operating Kubernetes reliably at scale is fundamentally an exercise in managing complexity. This paper has argued that Site Reliability Engineering supplies an appropriate framework for that task and has organized its practices into a coherent set of strategies. Measurable objectives, expressed as SLIs, SLOs, and error budgets, turn reliability from an aspiration into an engineering target. High-availability architecture, spanning a redundant control plane, topology-aware workload placement, and, where justified, multi-cluster topologies, removes single points of failure. Observability grounded in user-visible symptoms, capacity management that balances resilience against efficiency, resilience engineering through chaos experiments, and safe progressive delivery together reduce both the frequency and the impact of failure. Disciplined incident response and the systematic reduction of toil then convert operational experience into lasting improvement. Several challenges remain open. As platforms grow more heterogeneous, spanning multiple clouds, edge locations, and specialized hardware, maintaining consistent reliability guarantees becomes harder. Multi-tenancy intensifies the need for strong isolation without sacrificing efficiency. The increasing use of automation and machine learning in operations [6] raises new questions about how to keep automated remediation safe, observable, and accountable. Advancing reliability for these environments will require continued investment in tooling, abstractions, and the engineering culture that SRE represents.
[1] B. Beyer, C. Jones, J. Petoff, and N. R. Murphy, Eds., Site Reliability Engineering: How Google Runs Production Systems. Sebastopol, CA, USA: O'Reilly Media, 2016. [2] B. Beyer, N. R. Murphy, D. K. Rensin, K. Kawahara, and S. Thorne, Eds., The Site Reliability Workbook: Practical Ways to Implement SRE. Sebastopol, CA, USA: O'Reilly Media, 2018. [3] A. Verma, L. Pedrosa, M. Korupolu, D. Oppenheimer, E. Tune, and J. Wilkes, “Large-scale cluster management at Google with Borg,” in Proc. 10th Eur. Conf. Comput. Syst. (EuroSys), Bordeaux, France, 2015, pp. 1–17. [4] B. Burns, B. Grant, D. Oppenheimer, E. Brewer, and J. Wilkes, “Borg, Omega, and Kubernetes,” Commun. ACM, vol. 59, no. 5, pp. 50–57, May 2016. [5] Cloud Native Computing Foundation, “Kubernetes Documentation.” [Online]. Available: https://kubernetes.io/docs/ [6] P. K. Myakala, “How machine learning simplifies business decision-making,” Complexity Int. J. (CIJ), vol. 23, no. 3, pp. 407–410, 2019. [7] K. Hightower, B. Burns, and J. Beda, Kubernetes: Up and Running: Dive into the Future of Infrastructure. Sebastopol, CA, USA: O'Reilly Media, 2017. [8] C. Sridharan, Distributed Systems Observability: A Guide to Building Robust Systems. Sebastopol, CA, USA: O'Reilly Media, 2018. [9] A. Basiri, N. Behnam, R. de Rooij, L. Hochstein, L. Kosewski, J. Reynolds, and C. Rosenthal, “Chaos engineering,” IEEE Softw., vol. 33, no. 3, pp. 35–41, May/Jun. 2016. [10] B. Brazil, Prometheus: Up & Running. Sebastopol, CA, USA: O'Reilly Media, 2018. [11] L. A. Barroso, U. Hölzle, and P. Ranganathan, The Datacenter as a Computer: Designing Warehouse-Scale Machines, 3rd ed. San Rafael, CA, USA: Morgan & Claypool, 2018.
Publication Date
12/29/2020
Peer Review Type
Double-Blind Peer Review
Review Rounds: 2
Documents
Article Views
0
Total views since publication
PDF Downloads
8
Total downloads since publication
Geographic Reach
5
Digital Preservation: This article is permanently archived on Zenodo and complies with all data preservation standards across major indexing platforms.
Plagiarism Screening
This manuscript has been checked for plagiarism using TurnitinPlagiarismChecker software.
Conflict of Interest
The authors declare no conflict of interest related to this research work.
Funding Information
No funding information available for this research.
Related research in the same subject area
Loading similar articles...