Automated build from blog source

Author: github-actions[bot]

tech_blog/7.html

@@ -117,6 +117,14 @@ <h2 id="issue-5-flannel-does-not-work-after-a-while">😭 Issue 5: Flannel
 else that node will never be usable again? I really dont want to have to
 delete the node and add another one every time something happens! (maybe
 I should do this anyway as immutable deployments, but I digressed)</p>
+<p>I dont think this will be an issue with Calico though because the
+whole idea of k3s is it sets up as much of the management stuff as
+possible without spinning up a memory intensive constiner everywhere, it
+just runs in one process instead. This has the issue that managing
+things is a lot harder since every component in the process needs to be
+coordinated, and that is what kubernetes excells at, which is
+cordinating things, so there will be a lot of edge cases is you dont use
+kubernetes.</p>
 <p>What if I just dont use flannel at all, and install the well-loved
 Calico instead? Lickilly there is prescident for this, you just install
 k3s without a CNI, and bolt one on later</p>