DevOps(Day-48) : Kubernetes Important interview Questions - Part 1

 

  1. What is Kubernetes and why it is important?

    Kubernetes is the container orchestration tool. The container is used to package the application to run it in any system and this container's functionality is managed by Kubernetes.

    Some advantages are:-

    • Hosts containerized workloads, providing them with computing, storage, and network resources.

    • Automatically manages large numbers of containerized applications keeping them healthy and available by adapting to changes and challenges.

  2. What is the difference between docker swarm and Kubernetes?

    Docker Swarm is simple to set up and run. You can be off and running with creating services in moments. To manage a swarm, you use the same Docker command line interface you use to build images and run containers on your workstation. This makes for a greater degree of approachability for Docker users.

    Kubernetes uses a different command line interface. It has many similarities to the Docker interface, but it’s a separate executable with more commands to know. Kubernetes also has a vast array of configuration and authentication options. This gives much greater flexibility—but at the cost of having much more you need to know.

  3. How does Kubernetes handle network communication between containers?

    Components in a Kubernetes platform include nodes, applications, containers, and pods. These components communicate using different networking methods. The methods areas are shown below:-

    • Internet-to-service networking - Using the internet directly is critical. So, Ingress and egress techniques help to set up external access. These two policies are set up with either blacklisting or whitelisting to control traffic in and out of a network.

    • Container-to-container networking - It is straightforward for containers situated in the same pod to communicate with each other.

    • Pod-to-pod networking - Pods in Kubernetes are allocated a unique IP address which they use to communicate with each other.

    • Pod-to-service networking - Containers can go down at any moment, which may lead to the loss of all data stored in them. Same way, pods have IP addresses that may disappear unexpectedly. When this happens, Kubernetes replaces the lost IP addresses with new ones. So, each pod gets allocated a single IP address. An abstraction layer set on top of pods solves this problem. It helps communicate with the pods and eliminates the need to track pods as they start, die, and get rescheduled without affecting the application. Kubernetes services handle the abstraction layer. These services assign a single IP address to each set of pods. This enables the routing of traffic addressed to a pod through the virtual IP address of the service.

  4. How does Kubernetes handle the scaling of applications?

    Kubernetes uses Replicas to maintain the accountability of running Pods and ensures a fixed amount of Pods running each time. Even if due to some issues a Pod goes down, it automatically comes up. Based on CPU utilization K8s provides scalability to maintain application stability.

  5. What is a Kubernetes Deployment and how does it differ from a ReplicaSet?

    Kubernetes deployment is the methodology to rolling the updates of an application without making the services down. Deployment files have a set of features that define the application configurations and which include the replicas. ReplicaSets provides a set of replicas for the running Pods and on top of this additional configurations combine to form K8s deployment.

  6. Can you explain the concept of rolling updates in Kubernetes?

    The rolling update is the feature in K8s that allows the users to update the application without causing downtime. Rolling updates allow the following actions:

    • Promote an application from one environment to another (via container image updates)

    • Rollback to previous versions.

    • Continuous Integration and Continuous Delivery of applications with zero downtime

  7. How does Kubernetes handle network security and access control?

    Kubernetes uses the RBAC(RollBackAccessControl) method and a set of network policies to handle its network and access controls. Network Policies are defined to limit the traffic of external networks incoming to specific clusters. Access control policies restrict the access of unwanted users and allow only users with specific permissions.

  8. Can you give an example of how Kubernetes can be used to deploy a highly available application?

    Kubernetes uses Replicas in the Kubernetes configuration file which is responsible for making a fixed number of Pod available at all times. Let's say a Pod goes down to some issue then the application would become unstable and could go down. Here we define the replicas which contain the number of Pods that need to be available all time.

    Kubernetes Uses Load balancer that distributes incoming traffic between the Pods which makes the application highly available.

    Kubernetes uses network Policies that make prevents application vulnerability.

Thanks for reading my article. Have a nice day.

Comments

Post a Comment

Popular posts from this blog

DevOps(Day-97): Meta-Arguments in Terraform

Image
  TABLE OF CONTENTS Write about meta-arguments and their use in Terraform. Task-01: Meta-Arguments HandsOn Count for-each When you define a resource block in Terraform, by default, this specifies one resource that will be created. To manage several of the same resources, you can use either count or for_each, which removes the need to write a separate block of code for each one. Using these options reduces overhead and makes your code neater. count is what is known as a ‘meta-argument’ defined by the Terraform language. Meta-arguments help achieve certain requirements within the resource block. Write about meta-arguments and their use in Terraform. Meta-arguments in Terraform refer to a set of special arguments that can be used to define how a particular resource or module behaves within a Terraform configuration. These arguments provide additional configuration options and enable fine-grained control over the behaviour of resources or modules. Meta-arguments are prefixed with the...
Read more

DevOps(Day-95): Auto Scaling with Terraform

Image
  TABLE OF CONTENTS Understanding Scaling Pre-requisites Task 1: Create an Auto Scaling Group Task 2: Test Scaling Yesterday, we learned how to AWS S3 Bucket with Terraform. Today, we will see how to scale our infrastructure with Terraform. Understanding Scaling Scaling is the process of adding or removing resources to match the changing demands of your application. As your application grows, you will need to add more resources to handle the increased load. And as the load decreases, you can remove the extra resources to save costs. Terraform makes it easy to scale your infrastructure by providing a declarative way to define your resources. You can define the number of resources you need and Terraform will automatically create or destroy the resources as needed. Pre-requisites Create a  terraform.tf  file declaring the providers to be installed in the system according to the resources required. Create a  provider.tf  file to declare the region. Create a  vp...
Read more

DevOps (Day-1) Introduction

Image
  TABLE OF CONTENTS Infrastructure Automation Why DevOps is Important? What is DevOps? As the name indicates:- Dev + Ops = Development + Operations. Development i) Backend Developers ii) Front-end Developers iii) QA Operations i) System admins ii) Network admins iii) Database admins The practice of operations and development engineers participating together in the entire service lifecycle through a pipeline from design through the development process to production support. This process is known as DevOps. This is a process of automating the whole infrastructure. Now here comes a query, what are we automating? We are automating the whole team's work from the code-building stage to code deployment. Scenario 1:- In a company, there is a project in which developers are writing the code and deploying it to the QA environment frequently for each sprint. This code is then tested by the testing team. Suppose there is a situation of mishap happens where the testing team used the older code ...
Read more