DevOps with Kubernetes - Stephen Fleming

This is a very high-level overview of what DevOps is in the first section and then how Kubernetes works in the second section. While I hoped to glean something from this, it should have been a blog post. At least if it was a blog post the numerous spelling mistakes and grammar issues could have been fixed on the fly instead of forcing future readers to deal with the annoying issues.

If you're a manager with no technical background that wants to have some idea of what DevOps and Kubernetes is, this is a quick weekend read that will give you some basis for understanding. If you have any technical background at all, this is far too simplistic and you should skip it.

Purchase DevOps with Kubernetes on Amazon

- important [[devops]] tools Pg 32
- source code repository: [[git]]
- build server: automated server that builds your code into an executable form
- configuration management: puppet, chef, nixos style tool that defines how your environment will work
- virtual infrastructure: [[aws]], or google k8s
- test automation: what the name says, automated testing
- pipeline automation: describes the whole process above from written code to deploy
- Scrum sounds great and all but many of our retrospectives would be, I asked Jeff/Alex a question and heard nothing back so flailed around a bit. Pg 65
- [[kanban]] Pg 69
- Amazon, WalMart, Facebook are the examples of successful [[devops]] companies 106
- but really we’re nowhere near the size of these companies. Should we be using their tools if we don’t have their problems?

## Book 2 - Kubernetes Handbook Pg 113

- containers are fast and light, but they are also fragile and prone to a short lifespan Pg 122
- this is why we should always be running 2 pods for each site
- Secrets are for storing sensitive information and [[ConfigMaps]] are for storing general configuration information Pg 157
- Secrets are specifically best for storing less than 1MB of data like Pg 158
- keys, tokens, passwords
- when you updated a secret it is not automatically pulled to a pod, you must restart it to make sure the secret is available
- [[ConfigMaps]] are updated without needing to restart the pod
- they are **not** for storing sensitive information