<?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: V JAGADEESH CHARY </title>
    <description>The latest articles on Debug School by V JAGADEESH CHARY  (@jagadeeshchary31_265).</description>
    <link>https://www.debug.school/jagadeeshchary31_265</link>
    <image>
      <url>https://www.debug.school/images/CPDdQlGexClW9WOTxwLbEDeLKxuBxqind7bvkmstzXo/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly90aGVw/cmFjdGljYWxkZXYu/czMuYW1hem9uYXdz/LmNvbS9pLzk5bXZs/c2Z1NXRmajltN2t1/MjVkLnBuZw</url>
      <title>Debug School: V JAGADEESH CHARY </title>
      <link>https://www.debug.school/jagadeeshchary31_265</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/jagadeeshchary31_265"/>
    <language>en</language>
    <item>
      <title>devops day-2 assignment</title>
      <dc:creator>V JAGADEESH CHARY </dc:creator>
      <pubDate>Fri, 28 Apr 2023 06:50:47 +0000</pubDate>
      <link>https://www.debug.school/jagadeeshchary31_265/devops-day-2-assignment-1f4e</link>
      <guid>https://www.debug.school/jagadeeshchary31_265/devops-day-2-assignment-1f4e</guid>
      <description>&lt;p&gt;Docker commands:&lt;br&gt;
Port    - to interact with container from internet &lt;br&gt;
ps  - to list docker container details &lt;br&gt;
logs    - go get the logs from container (PID1)&lt;br&gt;
stats   - get the computation power details of container &lt;br&gt;
top     - to get the running processes details of container&lt;br&gt;
events  - to get the events logs from dockerd ( through events terminal)&lt;br&gt;
update  - to Update configuration of one or more containers (CPU and Memory)&lt;br&gt;
wait    - this holds the container process(like kill) till execute pipeline process of other container&lt;/p&gt;

&lt;p&gt;Image  : collection of file systems(root(user),app)&lt;/p&gt;

&lt;p&gt;       - docker gives unique name to each file system and will be downloaded to overlay2 folder&lt;br&gt;
       - we can call each file systems as layer , top layer will be root file system layer&lt;br&gt;
       - each layer will have parent layer and one parentless (root layer)&lt;br&gt;
       - all the layers are merged as one layer and mounted to container&lt;br&gt;
       - merged layer will be divided into two parts (diff, merge)&lt;br&gt;
                - merge - get attached to mount&lt;br&gt;
                - diff - changed to container files(merge) will be added to diff  &lt;br&gt;
       - if comment happens, new layer will be created from diff (read only) and its called new image (get-docker.sh)&lt;br&gt;
       - changes to the container (adding, deleting, modifying) in the merge will be added to diff location&lt;br&gt;
       - if new image from existing image ,it will be created from diff layer part as read only mode(new layer with combined old layers)&lt;br&gt;
       - Image creation can be implemented in two ways &lt;br&gt;
         -- all required layers in one layer(command)&lt;br&gt;
         -- each layer in each command (best practice)&lt;br&gt;
       - To share image locally (with same network) create tarball and can be shared name (save .tar and load commands)&lt;br&gt;
       - In order to share the create images with others ,will be uploaded in to repository (public,verivate)&lt;br&gt;
       - Most popular image repo is docker hub&lt;br&gt;
       - Login into docker hub through command line and by using tag ,can upload images to docker hub&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Kubernetes questions day 3</title>
      <dc:creator>V JAGADEESH CHARY </dc:creator>
      <pubDate>Wed, 26 Apr 2023 09:58:13 +0000</pubDate>
      <link>https://www.debug.school/jagadeeshchary31_265/kubernetes-questions-day-3-4pgg</link>
      <guid>https://www.debug.school/jagadeeshchary31_265/kubernetes-questions-day-3-4pgg</guid>
      <description>&lt;h2&gt;
  
  
  what is Kubernetes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Kubernetes is orchestration tool to manage the containers.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  why Kubernetes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Kubernetes is used for deploying and managing containerized applications. &lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Explained Kubernetes Architecture
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;It containers below components

&lt;ul&gt;
&lt;li&gt;API server: To process requests from client&lt;/li&gt;
&lt;li&gt;etcd :  storage unit with all API data with key value pair&lt;/li&gt;
&lt;li&gt;control manager: to control total process of orchestration. The API server is the front end for the Kubernetes control plane.&lt;/li&gt;
&lt;li&gt;scheduler: to schedule pods/containers. component that watches for newly created Pods with no assigned node and selects a node for them to run.&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Master components
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;API server, ETCD, Control manager, Scheduler &lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  worker components
&lt;/h2&gt;

&lt;p&gt;kubelet, container engine &lt;/p&gt;

&lt;h2&gt;
  
  
  workstation components
&lt;/h2&gt;

&lt;p&gt;kubelet with json or yaml&lt;/p&gt;

&lt;h2&gt;
  
  
  what is pod
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;basic logical unit of Kubernetes scheduler
&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Day 1 Docker - Assignment</title>
      <dc:creator>V JAGADEESH CHARY </dc:creator>
      <pubDate>Mon, 24 Apr 2023 19:15:17 +0000</pubDate>
      <link>https://www.debug.school/jagadeeshchary31_265/day-1-docker-assignment-4p14</link>
      <guid>https://www.debug.school/jagadeeshchary31_265/day-1-docker-assignment-4p14</guid>
      <description>&lt;h2&gt;
  
  
  What is Docker?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Docker is container management tool&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why We need docker?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;To save time (number of  applications can run at a time)- To save cost (CPU, less RAM ,storage,operational cost will be less) - Improve software quality (quality coding,quality testing)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is Container?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Container is lightweight (minimal resources) application runtime environment without kernel&lt;/li&gt;
&lt;li&gt;Container is resources created by namespaces and together powered by kernel&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How Container Works?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;docker will request kernel to create independent computational resources like network,PID,mount and username, those  all resources combined and creates a runtime environment.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When client request for docker image (if not available local,will be fetched from repo) and kernel will create user and will be assigned to computational resources like network,PID,mount and username&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to install Docker?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Docker provides convenience scripts at get.docker.com.&lt;/li&gt;
&lt;li&gt;Step 1 – Download and Run the script.&lt;/li&gt;
&lt;li&gt;$ curl -fsSL get.docker.com -o get-docker.sh&lt;/li&gt;
&lt;li&gt;$ sudo sh get-docker.sh&lt;/li&gt;
&lt;li&gt;Step 2 – Enable Docker&lt;/li&gt;
&lt;li&gt;$ sudo systemctl enable docker&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Step 3 – Start Docker&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;$ sudo systemctl start docker&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Step 4 – Verify that docker is installed correctly by running the hello-world image.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;$ sudo docker run hello-world&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What are the components docker?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;docker engine,docker images,registry,container&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is a container lifecycle commands?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;create,start,stop,restart,pause,unpause,kill,remove&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is docker pause/unpause?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;docker pause: Memory will be used but CPU allocations will be paused (no access to container)&lt;/li&gt;
&lt;li&gt;docker unpause: Memory will be used but CPU allocations will be re allocated ( access to container)&lt;/li&gt;
&lt;li&gt;this commands works with respect to accessing the resources&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is docker stop/kill?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;docker stop : graceful stopping (first child process will be killed, later parent process will be killed)&lt;/li&gt;
&lt;li&gt;docker kill :  forcefully kills the container ( Directly parent process will be killed )&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to get inside a container?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;by using shell&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to access container from outside?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;by using network&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is the rule for container is running?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;PID1 has to run with anything (because no kernel in the container) which should not be excited.&lt;/li&gt;
&lt;/ul&gt;

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