Explaining more about kubernetes flannel integration

Author: abacef

src/tech_blog/7.md

@@ -77,6 +77,8 @@ Describing the pods showed an error message
 
 This is a scary message, why was flannel not coming up? I checked and there is no file called `/run/flannel/subnet.env` on the node, even though there should be. I checked the other two nodes and yes they have this file. So that means I cannot restart the node at all or 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)
 
+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.
+
 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
 
 ```