https://www.katacoda.com/courses/kubernetes/launch-single-node-cluster https://training.linuxfoundation.org/resources/tutorials/set-up-a-ci-cd-pipeline-with-kubernetes-part-1-overview/

  >>  Kubernetes is an open-source system that handles the work of scheduling containers onto a compute cluster and manages the workloads to ensure they run as the user intends.
  >>  Kubernetes is an open source container Management tool which automates container deployment, container (de) scaling and container load balancing.
  >>  it works in all cloud vendors: Public,Hybrid & on-premises

Containers do not waste or block host resources unlike virtual machines. Containers have isolated libraries and binaries specific to the application they are running.

• Kubernets is not a docker

•       Docker      -->   Containerization platform
  

•       Kubernetes  -->   Conatiner manageable platform
  

•       Docker swarm also doing the same container manageable platform but auto scaling ,load balancing concept are missing . Manual intervention are required.
  

•       Kubernetes is not for simplle application architecture and preferrably for complex application
  

• Kubernetes is actually for,

• Kubernetes Vs Docker Swarm:

If any issue in any one of microservices then deployment is required only for that service after fixing the issue not all the services.

• Scaling:

        >>    Horizontal Pod Autoscale  - wil increase the no of pods
              The Horizontal Pod Autoscaler automatically scales the number of Pods in a replication controller, deployment, replica set or stateful set based on observed CPU utilization
        >>    Vertical Pod Autoscale  - will increase the cpu memory of pod
        >>    Cluster Autoscale       - will increase the kubernetes nodes
  

Kubernetes: Kubernetes utilizes its own YAML, API, and client definitions and each of these differ from that of standard docker equivalents. That is to say, you cannot utilize Docker Compose nor Docker CLI to define containers. While switching platforms, YAML definitions and commands need to be rewritten.

Docker Swarm: The Docker Swarm API doesn’t entirely encompass all of Docker’s commands but offers much of the familiar functionality from Docker. It supports most of the tools that run with Docker. Nevertheless, if Docker API is deficient of a particular operation, there doesn’t exist an easy way around it around swarm.

Kubernetes: Pods are exposed via service, which can be utilized as a load balancer within the cluster. Generally, an ingress is utilized for load balancing.

Docker Swarm: Swarm mode consists of a DNS element that can be utilized for distributing incoming requests to a service name. Services can be assigned automatically or can run on ports specified by the user.