DevOps KB Pages

User Story: A user story is a small, self-contained unit of development work designed to accomplish a specific goal within a product. A user story is usually written from the user’s perspective and follows the format: “ As [a user persona], I want [to perform this action] so that [I can accomplish this goal] .” References: https://www.productplan.com/glossary/user-story/#:~:text=A%20user%20story%20is%20usually,can%20accomplish%20this%20goal%5D.%E2%80%9D

You should stop writing Dockerfiles today — Do this instead https://medium.com/@akhilesh-mishra/you-should-stop-writing-dockerfiles-today-do-this-instead-3cd8a44cb8b0

Note: Services can also be defined without a selector label. A service can be directly matched to a pod by defining an endpoint with a static IP that has the same name as the service . The service will then connect directly to that IP. In this case, to troubleshoot the service, check if there is an endpoint in the cluster with the same name as the service. References: https://komodor.com/learn/kubernetes-service-examples-basic-usage-and-troubleshooting/#:~:text=Note%3A%20Services%20can%20also%20be,connect%20directly%20to%20that%20IP.

In Kubernetes a service always enables its network access to a pod or set of pods Services will select the pods based on their labels and when a network is made to those services it selects all Pods in the cluster matching the service’s selector and will choose one of them, and then will forwards the network request to it.   References: https://medium.com/avmconsulting-blog/service-types-in-kubernetes-24a1587677d6

These are collection of educational Kubernetes videos: How does Kubernetes create a Pod: https://www.youtube.com/watch?v=BgrQ16r84pM imperative vs declarative: https://www.youtube.com/watch?v=shqiLgbzIJY YAML File Explained - Deployment and Service: https://www.youtube.com/watch?v=qmDzcu5uY1I

Instead of memorizing all the Kubernetes configuration yaml Kind templates you may use the imperative commands to generate them.  To generate Kubernetes KIND templates simply use the Imperative wtih dry-run.  Depending on the command the dry-run can either be applied on the client side or on the server (api) side.   "Imperative commands are great for learning and interactive experiments, but they don't give you full access to the Kubernetes API. They're more commonly used to create YAML manifests and objects on the go. Declarative commands are useful for reproducible deployments and production." Here is an example of how to generate pod kind, YAML configuration file. kubectl run nginx --image=nginx:latest -o yaml --dry-run=client Here is an example of how to generate a service kind, YAML configuration file. kubectl create service clusterip my-svc --clusterip = "None" -o yaml --dry-run = client When working with declarative commands, you'll need a YAML m...