Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale.

One of the most popular options for managing container-based workload is Kubernetes.

Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse.

At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster.

On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling.

Finally, if an application needs to be updated, Kubernetes can stagger the update deployment to minimize downtime. Plus, if the update is problematic, Kubernetes can roll back to a previous version.

Along with pod management, Kubernetes can also manage container storage and networking. Kubernetes persistent volumes can be used to present data storage to one or more containers.

This configuration allows containers to read and write application data and persist this data across many pod instances.

That said, it is also common for an application running in Kubernetes to use cloud-based storage and data systems.

In regard to networking, Kubernetes network plugins provide capabilities such as exposing pods to the internet, load balancing traffic across multiple replicas of a pod, network isolation, and policy-driven network security.

These networking plugins also manage communication and name resolution between pods in the Kubernetes cluster. The capabilities of Kubernetes are not limited to the built-in features.

Additional capabilities can be created using a variety of methods for extending the Kubernetes API. With this flexibility, operators can be created to perform custom actions such as producing cloud events

on pod creation, providing custom pod scheduling logic and on-demand provisioning of managed cloud services, just to name a few.

The extension capabilities of Kubernetes make it a great platform on which to build SaaS services.

Know Kubernetes in depth here :

Kubeadm

Pods

Assign Pods to Node

ConfigMaps

Secrets

Replication Controller

ReplicaSet

Deployment

DaemonSet

Jobs

Namespaces

DashBoard UI

RBAC

Services

Volumes

Resource Quota

Liveness & Rediness

Kompose

Helm Charts

init Containers

Set security Contexts

Metrix Server

Upgrade

Operating System upgrades within Cluster

StatefulSet

Horizontal Pod Autoscaler

Monitoring,Troubleshooting

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more