Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Linux for Architects

You're reading from   Hands-On Linux for Architects Design and implement Linux-based IT solutions

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789534108
Length 380 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Denis Salamanca Denis Salamanca
Author Profile Icon Denis Salamanca
Denis Salamanca
Esteban Flores Esteban Flores
Author Profile Icon Esteban Flores
Esteban Flores
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

Preface 1. Section 1: High-Performance Storage Solutions with GlusterFS FREE CHAPTER
2. Introduction to Design Methodology 3. Defining GlusterFS Storage 4. Architecting a Storage Cluster 5. Using GlusterFS on the Cloud Infrastructure 6. Analyzing Performance in a Gluster System 7. Section 2: High-Availablility Nginx Web Application Using Kubernetes
8. Creating a Highly Available Self-Healing Architecture 9. Understanding the Core Components of a Kubernetes Cluster 10. Architecting a Kubernetes Cluster 11. Deploying and Configuring Kubernetes 12. Section 3: Elastic Stack
13. Monitoring with the ELK Stack 14. Designing an ELK Stack 15. Using Elasticsearch, Logstash, and Kibana to Manage Logs 16. Section 4: System Management Using Saltstack
17. Solving Management Problems with Salty Solutions 18. Getting Your Hands Salty 19. Design Best Practices 20. Assessments 21. Other Books You May Enjoy

Summary

In this chapter, we learned how to determine the compute and network requirements of a Kubernetes cluster. We also touched upon the software requirements that come along with it, such as etcd, and how odd-numbered clusters are preferred (due to the census algorithm) as the cluster needs to achieve more than 50% of votes for consensus.

The etcd cluster can either run on the kube-apiserver or have a separate set of clusters dedicated just for etcd. When it comes to resources, 2 CPUs and 8 GB of RAM should be enough. When deciding on the storage system for etcd, opt for lower latency and higher IOPS storage such as SSD. We then jumped into sizing the kube-apiserver, which can be run alongside etcd. Given that both components can coexist, resources should be bumped to anything between 8 and 16 GB of RAM and between 2 and 4 CPUs per node.

In order to properly size the worker...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime