Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Kubernetes in Production Best Practices
  • Table Of Contents Toc
  • Feedback & Rating feedback
Kubernetes in Production Best Practices

Kubernetes in Production Best Practices

By : Saleh, Karslioglu
5 (9)
close
close
Kubernetes in Production Best Practices

Kubernetes in Production Best Practices

5 (9)
By: Saleh, Karslioglu

Overview of this book

Although out-of-the-box solutions can help you to get a cluster up and running quickly, running a Kubernetes cluster that is optimized for production workloads is a challenge, especially for users with basic or intermediate knowledge. With detailed coverage of cloud industry standards and best practices for achieving scalability, availability, operational excellence, and cost optimization, this Kubernetes book is a blueprint for managing applications and services in production. You'll discover the most common way to deploy and operate Kubernetes clusters, which is to use a public cloud-managed service from AWS, Azure, or Google Cloud Platform (GCP). This book explores Amazon Elastic Kubernetes Service (Amazon EKS), the AWS-managed version of Kubernetes, for working through practical exercises. As you get to grips with implementation details specific to AWS and EKS, you'll understand the design concepts, implementation best practices, and configuration applicable to other cloud-managed services. Throughout the book, you’ll also discover standard and cloud-agnostic tools, such as Terraform and Ansible, for provisioning and configuring infrastructure. By the end of this book, you’ll be able to leverage Kubernetes to operate and manage your production environments confidently.
Table of Contents (12 chapters)
close
close

Destroying the cluster's resources

First, you should delete the ingress-nginx service to instruct AWS to destroy the NLB associated with the ingress controller. This step is required because terraform will fail to destroy this NLB because it has been created by Kubernetes:

$ kubectl -n nginx-ingress delete svc nginx-ingress

Then, you can follow the rest of the instructions in the Destroying the network and cluster infrastructure section in Chapter 3, Building and Provisioning Kubernetes Clusters, to destroy the Kubernetes cluster and all related AWS resources. Please ensure that the resources are destroyed in the following order:

  1. Kubernetes cluster packtclusters resources
  2. Cluster VPC resources
  3. Terraform shared state resources

By executing the previous steps, all Kubernetes and AWS infrastructure resources should be destroyed and cleaned up ahead of the hands-on practice in the next chapter.

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY