Dockers aren’t really a new thing around, but in many cases developers are spending time to create proper image or trying different Dockerfile configurations, or simply they don’t pay attention to re-usability and multi environment build.

Consider a Kubernetes cluster with 3 worker nodes having a memory of 10GB each. Suppose the developers end up deploying some pods by mistake which consumes almost all the cpu and memory available in the node. Hence causing resource contention in the others application pods which serves traffic from consumers. This could also be caused when hackers inject high resource consuming pods intentionally into the system.

Docker provides the ability to package and run an application in a loosely isolated environment called a container.

In this post you'll learn how to configure a development environment with live-reload enabled. This will allow you to convert a legacy application so it uses Docker, Docker volumes, and docker-compose.

As new technologies come out, we don’t even hesitate to use them. Docker is one of them, its benefits are very, very much! So, do you know about the security holes that Docker operating systems you use?

Building simple automation through Github & Dockerhub Auto build to build containers and then deploy it to GKE through Kubernetes Manifest:

Medium’s largest and most followed independent DevOps publication. Join thousands of aspiring developers and DevOps enthusiasts

The main goal of this tutorial is to provide the audience with sufficient background to enable -and encourage- them to take their first steps in the usage of these tools. No previous technical knowledge will be assumed. This tutorial intends to guide readers through the process of installation and implementation of an Azure Function in a Docker Container.

Troubleshoot your Kubernetes application with ease and understand its mechanics

In this post I describe a problem I had running IdentityServer 4 behind an Nginx reverse proxy. In my case, I was running Nginx as an ingress controller for a Kubernetes cluster, but the issue is actually not specific to Kubernetes, or IdentityServer - it's an Nginx configuration issue.