<?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>DEV Community: Abhijit Ezhava</title>
    <description>The latest articles on DEV Community by Abhijit Ezhava (@abhijitez).</description>
    <link>https://dev.to/abhijitez</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F318537%2Fcb1a7892-8993-40e5-9d24-29cbd0d4c556.png</url>
      <title>DEV Community: Abhijit Ezhava</title>
      <link>https://dev.to/abhijitez</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abhijitez"/>
    <language>en</language>
    <item>
      <title>display: inline magic space!</title>
      <dc:creator>Abhijit Ezhava</dc:creator>
      <pubDate>Mon, 26 Sep 2022 15:41:01 +0000</pubDate>
      <link>https://dev.to/abhijitez/display-inline-magic-space-2caa</link>
      <guid>https://dev.to/abhijitez/display-inline-magic-space-2caa</guid>
      <description>&lt;p&gt;Ever wondered when you adding a image to a HTML, you might find little space around it. It's not border, margin, padding, width or height; than what is it.&lt;/p&gt;

&lt;p&gt;In html, images are treated as inline by default, so image's are generally text in mind of html and as usual text has spacing between them. The addition height is because of the line height, which can be removed by adding this &lt;code&gt;line-height: 0&lt;/code&gt; or making the image tag to display: block. I personally like the first approach as this doesn't change the flow of the element.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why not use custom nginx pod rather than using Ingress nginx on Kubernetes?</title>
      <dc:creator>Abhijit Ezhava</dc:creator>
      <pubDate>Sun, 11 Sep 2022 06:40:09 +0000</pubDate>
      <link>https://dev.to/abhijitez/why-not-use-custom-nginx-pod-rather-than-using-ingress-nginx-on-kubernetes-1c4d</link>
      <guid>https://dev.to/abhijitez/why-not-use-custom-nginx-pod-rather-than-using-ingress-nginx-on-kubernetes-1c4d</guid>
      <description>&lt;h3&gt;
  
  
  Old school nginx
&lt;/h3&gt;

&lt;p&gt;The past approach of the writing custom config of ngnix which basically points to the cluster-ip service of the different deployment has many limitation, one of the reason it doesn’t support sticky session and have control overs the pods as the service is attached to cluster-ip service rather the one on one pods.&lt;/p&gt;

&lt;h3&gt;
  
  
  Comes the hero; Ingress Nginx
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;ingress-nginx&lt;/code&gt; is a wrapper over nginx created by Kubernetes team. It directly routes the request to the POD IP:PORT rather than making the connection with Service Object.&lt;br&gt;
As this comes with advantage like sticky session, controlling the routes on pods level and having broader control over the request and response modal.&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>nginx</category>
      <category>ingress</category>
      <category>docker</category>
    </item>
  </channel>
</rss>
