Search icon CANCEL
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
Introduction to DevOps with Kubernetes

You're reading from   Introduction to DevOps with Kubernetes Build scalable cloud-native applications using DevOps patterns created with Kubernetes

Arrow left icon
Product type Paperback
Published in May 2019
Publisher
ISBN-13 9781789808285
Length 374 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Süleyman Akbaş Süleyman Akbaş
Author Profile Icon Süleyman Akbaş
Süleyman Akbaş
Onur Yılmaz Onur Yılmaz
Author Profile Icon Onur Yılmaz
Onur Yılmaz
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Chapter 1: Introduction to DevOps 2. Chapter 2: Introduction to Microservices and Containers FREE CHAPTER 3. Chapter 3: Introduction to Kubernetes 4. Chapter 4: Creating a Kubernetes Cluster 5. Chapter 5: Deploy an Application to Kubernetes 6. Chapter 6: Configuration and Storage Management in Kubernetes 7. Chapter 7: Updating and Scaling an Application in Kubernetes 8. Chapter 8: Troubleshooting Applications in Kubernetes 9. Chapter 9: Monitoring Applications in Kubernetes Appendix

Secret Management Best Practices

In this section, we'll go through some secret management best practices. These points are essential to understand in order to manage secrets in a DevOps environment. The following figure shows secret management best practices, which are valuable practices for securing sensitive information:

Figure 6.7: Secret management best practices
Figure 6.8: Secret management best practices

Identifying Secrets

The very first step for secret management is to identify all kinds of secrets. They include, but are not limited to, passwords, SSH keys, and certificates for communication (for example, TLS). It is very important that this should be a continuous process. That is, all new configuration values should be evaluated and treated as secret if they include any sensitive information. Also, secrets should be constrained to have enough complexity to make them difficult to solve. For example, when you integrate your application with another one, you'd usually need a kind...

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 €18.99/month. Cancel anytime