1. What is ReplicasSets?

A ReplicaSet is a process that runs multiple instances of a Pod and keeps the specified number of Pods constant. Its purpose is to maintain the specified number of Pod instances running in a cluster at any given time

2. How to work with ReplicasSets?

 It is defined with fields. If we give the number of replicas in yaml file it will created those many.

When a ReplicaSet needs to create new Pods, it uses its Pod template.

3. Example of ReplicasSets?

Below code will help me create 2 replicas for my replicaset

apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: my-replicaset
spec:
  replicas: 2
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
      - name: my-container
        image: nginx

Assignment – 2

1. What is DeamonSets?

A DaemonSet ensures that all (or some) Nodes run a copy of a Pod. As nodes are added to the cluster, Pods are added to them. As nodes are removed from the cluster, those Pods are garbage collected. Deleting a DaemonSet will clean up the Pods it created.

2. How to work with DeamonSets?

• When a new node is added to a Kubernetes cluster, a new pod will be added to that newly attached node.
• When a node is removed, the DaemonSet controller ensures that the pod associated with that node is garbage collected. Deleting a DaemonSet will clean up all the pods that DaemonSet has created.
• Depending on the requirement, you can set up multiple DaemonSets for a single type of daemon, with different flags, memory, CPU, etc. that supports multiple configurations and hardware types.

3. Example of DeamonSets?

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: test-daemonset
  namespace: test-daemonset-namespace
  Labels:
    app-type: test-app-type
spec:
  template:
    metadata:
      labels:
        name: test-daemonset-container
  selector:
    matchLabels:
      name: test-daemonset-container

The apiVersion, kind, and metadata are required fields in every Kubernetes manifest. The DaemonSet specific fields come under the spec section—these fields are both mandatory.

Template and selector

Assignment – 3

1. What is Statefulsets?

StatefulSet is the workload API object used to manage stateful applications.Manages the deployment and scaling of a set of Pods, and provides guarantees about the ordering and uniqueness of these Pods.

2. How to work with Statefulsets?

StatefulSets are valuable for applications that require one or more of the following.

• Stable, unique network identifiers.
• Stable, persistent storage.
• Ordered, graceful deployment and scaling.
• Ordered, automated rolling updates.

3. Example of Statefulsets?

apiVersion: v1
kind: Service
metadata:
  name: nginx
  labels:
    app: nginx
spec:
  ports:
  - port: 80
    name: web
  clusterIP: None
  selector:
    app: nginx
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web
spec:
  selector:
    matchLabels:
      app: nginx # has to match .spec.template.metadata.labels
  serviceName: "nginx"
  replicas: 3 # by default is 1
  template:
    metadata:
      labels:
        app: nginx # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: nginx
        image: k8s.gcr.io/nginx-slim:0.8
        ports:
        - containerPort: 80
          name: web
        volumeMounts:
        - name: www
          mountPath: /usr/share/nginx/html
  volumeClaimTemplates:
  - metadata:
      name: www
    spec:
      accessModes: [ "ReadWriteOnce" ]
      storageClassName: "my-storage-class"
      resources:
        requests:
          storage: 1Gi

In the above example:

• A Headless Service, named nginx, is used to control the network domain.
• The StatefulSet, named web, has a Spec that indicates that 3 replicas of the nginx container will be launched in unique Pods.
• The volumeClaimTemplates will provide stable storage using PersistentVolumes provisioned by a PersistentVolume Provisioner.

The name of a StatefulSet object must be a valid DNS subdomain name.

Assignment – 4

1. What is Service?

A Kubernetes service is a logical abstraction for a deployed group of pods in a cluster (which all perform the same function).

Since pods are ephemeral, a service enables a group of pods, which provide specific functions (web services, image processing, etc.) to be assigned a name and unique IP address (clusterIP).

2. How Service Works?

A Kubernetes service can be used to easily expose an application deployed on a set of pods using a single endpoint. A service is both a REST object and an abstraction that defines:

• A set of pods
• A policy to access them

3. What are the types of Service?

• ClusterIP. Exposes a service which is only accessible from within the cluster.
• NodePort. Exposes a service via a static port on each node’s IP.
• LoadBalancer. Exposes the service via the cloud provider’s load balancer.
• ExternalName. Maps a service to a predefined externalName field by returning a value for the CNAME record.

4. Example Yaml of Service

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  selector:
    app: MyApp
  ports:
    - protocol: TCP
      port: 80
      targetPort: 9376

This specification creates a new Service object named “my-service”, which targets TCP port 9376 on any Pod with the app=MyApp label.

Assignment – 5

1.What is Loadbalancer?

Load balancing is defined as the methodical and efficient distribution of network or application traffic across multiple servers in a server farm

2. What are the types of Loadbalancer?

3. How Loadbalancer works?

Each load balancer sits between client devices and backend servers, receiving and then distributing incoming requests to any available server capable of fulfilling them.

Assignment – 6

1. What is Discovery Services?

Service discovery takes advantage of the labels and selectors to associate a service with a set of pods.

2. How Discovery Services works?

A single pod or a ReplicaSet may be exposed to internal or external clients via services, which associate a set of pods with a specific criterion. Any pod whose labels match the selector defined in the service manifest will automatically be discovered by the service. This architecture provides a flexible, loosely-coupled mechanism for service discovery.

3. What is CoreDNS?

CoreDNS is a flexible, extensible DNS server that can serve as the Kubernetes cluster DNS. Like Kubernetes, the CoreDNS project is hosted by the CNCF.

4. Use of CoreDNS?

CoreDNS is a flexible, extensible DNS server that can serve as the Kubernetes cluster DNS. … You can use CoreDNS instead of kube-dns in your cluster by replacing kube-dns in an existing deployment, or by using tools like kubeadm that will deploy and upgrade the cluster for you

1.Storage Orchestration

2.Service discovery and load balancing

3.Automated rollouts/roll backs

4. Self healing

5. Automatic bin packaging

6. Secret &config management

2. Master Node components

1.Kube-controller – controller of ontrollers (node/endpoints/namespaces)

2. Schedular – Assign work to nodes

3.Api server – Front end to control plane

4.Cluster store –

3. Worker node components

1.Kubelet

2.namespace

4. How Kubernetes works?

It will work through Master and worker node. If we have 4 master components we can beome a master and node will have multiple pods and containers.

If you are deployinga package in kubernetes with the help of 4 master components it will deploy them to PODs (2hich internally had containers)

5. Components of workstation.

Comprises of Master node and worker node.

6. What is POD? Explain in 20 BULLET LINE.

1. Pods are the deployable units that you can create and manage in Kubernetes.
2. It containes  one or more containers
3. A Pod is a set of namespaces, cgroups,
4. Pods can have single container/multiple container.
5. A POD can have 2 different container but not the same.
6. A Pod is not a process, but an environment for running container(s). A Pod persists until it is deleted.

Step2: Pre Test using LMS: Sent screenshot to Shiva

Step 3 – Install Docker Engine in Centos#1 Vm.

[root@ip-172-31-2-102 centos]# history
    1  vi /etc/ssh/sshd_config
    2  passwd centos
    3  systemctl restart sshd
    4  systemctl restart sshd
    5  passwd centos
    6  vi /etc/ssh/sshd_config
    7  systemctl restart sshd
    8  passwd centos
    9  exit
   10  sudo yum install -y yum-utils device-mapper-persistent-data lvm2
   11  sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
   12  sudo yum install –y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
   13  sudo yum-config-manager --enable rhui-REGION-rhel-server-extras
   14  sudo yum install -y docker-ce
   15  sudo yum install docker-ce
   16  docker -v
   17  sudo systemctl enable docker
   18  ps -ef|grep docker
   19  sudo systemctl start docker
   20  docker info
   21  sudo docker run hello-world
   22  docker info
   23  history
[root@ip-172-31-2-102 centos]# sudo systemctl enable docker
[root@ip-172-31-2-102 centos]# sudo systemctl start docker
[root@ip-172-31-2-102 centos]# sudo docker run hello-world
[root@ip-172-31-2-102 centos]# docker ps -a
CONTAINER ID   IMAGE         COMMAND    CREATED          STATUS                      PORTS     NAMES
3c346de20dfd   hello-world   "/hello"   2 minutes ago    Exited (0) 2 minutes ago              elastic_bardeen
8545a66d0a03   hello-world   "/hello"   14 minutes ago   Exited (0) 14 minutes ago             ecstatic_kilby
[root@ip-172-31-2-102 centos