Book Image

Edge Computing Systems with Kubernetes

By : Sergio Méndez
Book Image

Edge Computing Systems with Kubernetes

By: Sergio Méndez

Overview of this book

Edge computing is a way of processing information near the source of data instead of processing it on data centers in the cloud. In this way, edge computing can reduce latency when data is processed, improving the user experience on real-time data visualization for your applications. Using K3s, a light-weight Kubernetes and k3OS, a K3s-based Linux distribution along with other open source cloud native technologies, you can build reliable edge computing systems without spending a lot of money. In this book, you will learn how to design edge computing systems with containers and edge devices using sensors, GPS modules, WiFi, LoRa communication and so on. You will also get to grips with different use cases and examples covered in this book, how to solve common use cases for edge computing such as updating your applications using GitOps, reading data from sensors and storing it on SQL and NoSQL databases. Later chapters will show you how to connect hardware to your edge clusters, predict using machine learning, and analyze images with computer vision. All the examples and use cases in this book are designed to run on devices using 64-bit ARM processors, using Raspberry Pi devices as an example. By the end of this book, you will be able to use the content of these chapters as small pieces to create your own edge computing system.
Table of Contents (21 chapters)
1
Part 1: Edge Computing Basics
7
Part 2: Cloud Native Applications at the Edge
13
Part 3: Edge Computing Use Cases in Practice

Pros and cons of Traefik, NGINX, and Contour

All the ingress controllers have the basic features to expose your application, that is, they are compatible with the Ingress object in Kubernetes. So, let’s explore the pros and cons of each Ingress controller. Let’s get started with this quick comparison:

  • NGINX Ingress is an ingress controller that uses NGINX to expose applications in your cluster.
    • Pros: It is the most widely used ingress controller for Kubernetes. It has a lot of documentation. Developer and community support is widely available. The community behind it is bigger than Traefik and Contour.
    • Cons: It can be slow compared to Envoy-based ingress controllers such as Emissary, Gloo, and Contour.
  • Traefik is an ingress controller created by Traefik Labs. It has a lot of features, which can be used as plugins. It can be used to visualize your applications on a dashboard.
    • Pros: It has a dashboard and a lot of documentation. It also has some service mesh capabilities...