DevOps Madness

Hey, a guy I respect in DevOps told me micro services that implement liveness prob and readiness prob is a good thing to do in a Kubernetes environment. That sounds obvious but if an app is in ready state, would that also means it is a live?  Why the curve ball?  Well, container state machine goes like startup -?-> liveness -?-> readiness then the pod is up and running.  It is generally consider bad to send traffic to pod that is not ready to process data.  Otherwise, it can cause data lost if proper exception handling is not in place or that reliable connection is assumed like UDP traffic.  Liveness prob is there to detect pod in bad state and restart it to gain more use out of iffy pod hosting application of questionable quality.  Emm, that sound like making the best of bad situation until someone is notified.  For a pod to transition from one state to another, there needs to be some conditions meet.  What is the condition transitioning fr...

The problem with DevOps is there are too many technology to know.  The only way to manage DevOps work is follow some principles.  Here are some principles: Build self service infrastructure Build evolvable infrastructure Be anti-expertise Build disposable infrastructure Over communicate Do no harm Pay down technical debts AWS is a totally self service infrastructure.  They have great documentation, their GUI is intuitive, and they have great support to show you how things are done.  I can pretty much compose infrastructure on my own in AWS without needing to ask AWS engineers to build stuff for me.  Granted from time to time, I need to ask them to increase quotas.  DevOps should aim to provide same level of service to internal customers.  DevOps tools are constantly evolving, GitOps has gain acceptance in the field and it is a great thing.  GitOps is a great help in moving DevOps services toward a self service model.  Just do it until a b...