Kubernetes Basics for DevOps Engineers

<p>Disclaimer: this is not a post from a seasoned DevOps engineer. So if you also know very little about Kubernetes, ignorance loves company.</p> <p>To start with some (somewhat)

<p>Kubernetes can look intimidating when you first encounter it.</p> <p>You see:<br /> </p> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>kubectl

<p>If you have already explored <a href="https://bibekkakati.com/blog/docker-explained-containers-and-architecture" rel="noopener noreferrer">Docker</a>, you know how convenient

<p>Kubernetes Concepts are not random; each one has a beautiful problem-solving story behind it. </p> <p>Most people learn Kubernetes the wrong way.</p> <p>They see it as a list

<p><a class="article-body-image-wrapper"

<p>The Problem Nobody Talks About<br /> When I first approached Kubernetes, every tutorial assumed I was a developer coming from Docker. Nobody wrote for someone who knew vSphere

<p><strong>If you’ve ever deployed an app on Kubernetes and thought</strong>:<br /> “Okay… my Pods are running, but how do I actually reach them?”<br /> Then you’re exactly where

<p>Like Docker, Kubernetes is one of those words I see being thrown around, and I've always been curious about it. Which is one of the reasons why I decided to do Machine Learning