Book Image

IoT Edge Computing with MicroK8s

By : Karthikeyan Shanmugam
Book Image

IoT Edge Computing with MicroK8s

By: Karthikeyan Shanmugam

Overview of this book

Are you facing challenges with developing, deploying, monitoring, clustering, storing, securing, and managing Kubernetes in production environments as you're not familiar with infrastructure technologies? MicroK8s - a zero-ops, lightweight, and CNCF-compliant Kubernetes with a small footprint is the apt solution for you. This book gets you up and running with production-grade, highly available (HA) Kubernetes clusters on MicroK8s using best practices and examples based on IoT and edge computing. Beginning with an introduction to Kubernetes, MicroK8s, and IoT and edge computing architectures, this book shows you how to install, deploy sample apps, and enable add-ons (like DNS and dashboard) on the MicroK8s platform. You’ll work with multi-node Kubernetes clusters on Raspberry Pi and networking plugins (such as Calico and Cilium) and implement service mesh, load balancing with MetalLB and Ingress, and AI/ML workloads on MicroK8s. You’ll also understand how to secure containers, monitor infrastructure and apps with Prometheus, Grafana, and the ELK stack, manage storage replication with OpenEBS, resist component failure using a HA cluster, and more, as well as take a sneak peek into future trends. By the end of this book, you’ll be able to use MicroK8 to build and implement scenarios for IoT and edge computing workloads in a production environment.
Table of Contents (24 chapters)
1
Part 1: Foundations of Kubernetes and MicroK8s
4
Part 2: Kubernetes as the Preferred Platform for IOT and Edge Computing
7
Part 3: Running Applications on MicroK8s
14
Part 4: Deploying and Managing Applications on MicroK8s
21
Frequently Asked Questions About MicroK8s

Performing rolling updates to the application with a new software version

The rolling updates feature of Kubernetes allows Deployments to be updated with zero downtime. It handles the upgrading of pods' instances with new ones in an incremental manner, and new pods would be scheduled on Nodes that have resources available.

Some key features of rolling updates are listed here:

  • Transferring an application from one environment to another (via container image updates).
  • Rollback to a prior version of the application.
  • With minimal downtime, continuous integration and continuous delivery (CI/CD) of applications are achievable.

We are going to reuse the same example of the nginx sample deployment that we used earlier. We can update the same deployment by applying the following new YAML file.

This YAML file specifies that the deployment should be updated to use the nginx 1.16.1 container image instead of nginx.1.14.2:

apiVersion: apps/v1
kind: Deployment...