<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Debug School: Ayush Sinha</title>
    <description>The latest articles on Debug School by Ayush Sinha (@ayush5588).</description>
    <link>https://www.debug.school/ayush5588</link>
    <image>
      <url>https://www.debug.school/images/IHXveyOQ6OUaJV1rBhRqCRxOQxtBnRiMeq_OiNYwQqA/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzE0Ni9kODAz/ZjIwZi01YmNkLTRk/NDctYTBiNC0yNDI3/NzNjYmU5NDUucG5n</url>
      <title>Debug School: Ayush Sinha</title>
      <link>https://www.debug.school/ayush5588</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/ayush5588"/>
    <language>en</language>
    <item>
      <title>k8s Assignment 2</title>
      <dc:creator>Ayush Sinha</dc:creator>
      <pubDate>Tue, 18 Oct 2022 07:06:00 +0000</pubDate>
      <link>https://www.debug.school/ayush5588/k8s-assignment-2-m7m</link>
      <guid>https://www.debug.school/ayush5588/k8s-assignment-2-m7m</guid>
      <description>&lt;h3&gt;
  
  
  Kubernetes Architecture
&lt;/h3&gt;

&lt;p&gt;A kubernetes cluster consists of a master node(s) (aka control plane) and worker node(s). Job of the &lt;strong&gt;master node&lt;/strong&gt; is to manage the worker nodes. This is done through different components running in the form of pods on it. Job of the &lt;strong&gt;worker node&lt;/strong&gt; is to run the workload (i.e. application). These applications are running inside container which with some other components form a pod. &lt;/p&gt;

&lt;h4&gt;
  
  
  Master Node
&lt;/h4&gt;

&lt;ol&gt;
&lt;li&gt;Also known as Control plane. &lt;/li&gt;
&lt;li&gt;It's job is to manage the worker nodes. &lt;/li&gt;
&lt;li&gt;To help the master node in managing the worker nodes, there are 4 different components: API Server, scheduler, controller manager and etcd. &lt;/li&gt;
&lt;/ol&gt;

&lt;h4&gt;
  
  
  Worker Node
&lt;/h4&gt;

&lt;ol&gt;
&lt;li&gt;It's job is to run the applications in the form of pods. &lt;/li&gt;
&lt;li&gt;It consists of kubelet, kube-proxy, container-runtime, pods, etc. &lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>10 problems solved by kubernetes</title>
      <dc:creator>Ayush Sinha</dc:creator>
      <pubDate>Tue, 18 Oct 2022 04:53:07 +0000</pubDate>
      <link>https://www.debug.school/ayush5588/10-problems-solved-by-kubernetes-12co</link>
      <guid>https://www.debug.school/ayush5588/10-problems-solved-by-kubernetes-12co</guid>
      <description>&lt;ol&gt;
&lt;li&gt;Orchestration of millions of containers running in parallel. &lt;/li&gt;
&lt;li&gt;Rolling out new version upgrade without manual intervention. &lt;/li&gt;
&lt;li&gt;Automatic scaling of the infrastructure based on the workload. &lt;/li&gt;
&lt;li&gt;Cost savings because of the autoscaling feature. &lt;/li&gt;
&lt;li&gt;Provides High Availability (HA) for the running applications. &lt;/li&gt;
&lt;li&gt;Support for managing applications on multiple cloud. &lt;/li&gt;
&lt;li&gt;Make it easy for porting of application from one infrastructure to other. &lt;/li&gt;
&lt;li&gt;Lifecycle management of services (running in containers form) for the microservice based applications. &lt;/li&gt;
&lt;li&gt;Allows developers to focus on the application logic rather  than focusing on the management of the applications to be run. &lt;/li&gt;
&lt;li&gt;Provide load balancing feature to handle large incoming requests. &lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Docker Assignment</title>
      <dc:creator>Ayush Sinha</dc:creator>
      <pubDate>Mon, 17 Oct 2022 20:20:33 +0000</pubDate>
      <link>https://www.debug.school/ayush5588/docker-assignment-1ap2</link>
      <guid>https://www.debug.school/ayush5588/docker-assignment-1ap2</guid>
      <description>&lt;h4&gt;
  
  
  Docker &lt;strong&gt;pause&lt;/strong&gt; &amp;amp; &lt;strong&gt;unpause&lt;/strong&gt; commands
&lt;/h4&gt;

&lt;h5&gt;
  
  
  &lt;em&gt;docker pause&lt;/em&gt;
&lt;/h5&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt; * This command is used to suspend / stay / pause all the 
   running processes in the given container. 
 * When the docker daemon is asked to pause the 
   container, it performs certain state checks on the 
   container such as:
     1. Whether the container is in running state or not. 
     2. Whether the container is already paused. 
     3. Whether the container is in restarting phase. 
 * Command: docker pause container_id/container_name
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;h5&gt;
  
  
  &lt;em&gt;docker unpause&lt;/em&gt;
&lt;/h5&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;* This command moves the status of the container to 
  "Running" from "Paused". 
* Command: docker unpause container_id/container_name
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;h4&gt;
  
  
  Docker &lt;strong&gt;stop&lt;/strong&gt; &amp;amp; &lt;strong&gt;kill&lt;/strong&gt; commands
&lt;/h4&gt;
&lt;h5&gt;
  
  
  &lt;em&gt;docker stop&lt;/em&gt;
&lt;/h5&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  * This command issues a SIGTERM signal which stops the 
    program gracefully unlike the KILL command. 
  * Command: docker stop container_id/container_name
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;h5&gt;
  
  
  &lt;em&gt;docker kill&lt;/em&gt;
&lt;/h5&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  * This command issues a SIGKILL signal which stops the 
    program abruptly by killing the entry process 
    (process belonging to pid1). 
  * Command: docker kill container_id/container_name
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
  </channel>
</rss>
