Learning DevOps made Easier

Image credit :  Platformer -   https://medium.com/platformer-blog/using-kubernetes-secrets-5e7530e0378a Introduction: Kubernetes is currently the de-facto standard for container orchestration. As organizations globally are adopting a Container first development approach, a large part of existing workloads is still running on virtual machines, be in the public cloud or a private data center. Hence a lot of companies are now facing severe challenges in migrating from their old methods to Kubernetes. However, there are times when you want bake-in sensitive secret information into your Kubernetes cluster and share it across when needed. You do not want to put this information into a Pod definition YAML or a docker image. This is where Kubernetes Secret comes to your rescue. In this post, we will try to gain more insight into how we can manage secrets effectively in Kubernetes. Why Use a Secret? Not all configuration information is safe to keep out in the “pu...

When talking about “ service mesh ” in a container and Kubernetes ecosystem, I am sure you would definitely have heard of the  Istio  tool It has become the most popular and widely used service meshes to secure and control network traffic in container space. If you follow this space, you must be aware that the Istio team puts-in a lot of hard work to update and come up with new releases, the latest one being Istio v1.5. So in this post, I am going to share what changes or updates Istio v1.5 brings for you. At a high level, as  Istio team puts it as  : “We’ve made it simpler to install and run Istio by consolidating the control plane components into a single binary; we’ve introduced a powerful and fast new extension model for proxy servers across the industry, and we’ve continued to improve usability, security, telemetry and traffic control. ” Major Updates in the new release 1. A major change to control plane architecture, with Is...

Today , I am going to share with you all, some of the commonly used Docker commands.  Docker Cheatsheet: $ docker version                               to know the current docker version $ docker version — format ‘{{.Server.Version}}’ . to get the server version Docker Container Lifecycle: $ docker create     creates a container but does not start it $ docker rename     allows the container to be renamed $ docker run           creates and starts a container in one operation $ docker rm             deletes a container $ docker rm -v    delete container and also remove the volumes associated with the container Starting & Stopping a Docker container $ docker starts      starts a container so it is running $ docker stop         ...

Generally whenever we talk about  Devops , we are mostly focussed on faster and continuous deployment, automation and monitoring the system for errors and failures. At times, what we often tend to neglect is the “ Testing ” part of a Devops implementation. So today I am going to discuss a bit about the “Left Shift” principle and how to do it in Devops way. I know that it is not a new concept but for those of you who do not know the “Left Shift” principle, let me try to elaborate. What do we actually mean by “Shifting Left”? Consider a regular software lifecycle, which typically moves from Left to Right :  Design >> Develop >> Test >> Deployment >> Production Monitoring So the “ Left Shift ” concept emphasis that the more effort that is shifted towards left or earlier in the lifecycle process, the less chances or errors or failures. In simple words, it talks about identifying the bugs and errors at an early stage (Left side)...

What is DevOps all about? For a Non-Devops person Currently we see a lot of buzzword in the market for " Devops ".  I am sure all of us would have heard of this term somewhere or the other, but how many of us do understand it or know what is it? So this blog is an attempt to help all those people who have definitely heard about DevOps, but do not understand: 1.  What 2.  How 3.  When & Where of DevOps So I would like to share with all of you , what all little knowledge and understanding I have of Devops.