Rallias 
Ok, why does Kubernetes have to be so complicated to setup?
Like, seriously, how the fuck am I supposed to choose a networking policy?
Oh, there's k3s.
I'm going to be fucking lazy then.
More false promises of ease.
I think they do actually pull off ease, but good lord there's so much that needs setting up... If it weren't for my desire to use fairly industry standard components, I'd simply use lxc and rig up everything myself.
And, like, I hate that about myself, that my gut instinct is to return to the paradigm in familiar with, but fucking hell, why?
Like, networking... I just want a bridge with nat. Why do I need to make some sort of informed decision on whether I want fluffy or cuttlefish just in order to get networking?
And once k3s has chosen network for me, how do I launch an instance? Oh, I need to choose storage? Why can't it just shove it in a box? Why do I have to baby it every step of the way?
Travis KJ5DCLIf your just have a single node, start with https://kubernetes.io/docs/concepts/storage/volumes/#local
Volumes
Kubernetes volumes provide a way for containers in a pod to access and share data via the filesystem. There are different kinds of volume that you can use for different purposes, such as: populating a configuration file based on a ConfigMap or a Secret providing some temporary scratch space for a pod sharing a filesystem between two different containers in the same pod sharing a filesystem between two different pods (even if those Pods run on different nodes) durably storing data so that it stays available even if the Pod restarts or is replaced passing configuration information to an app running in a container, based on details of the Pod the container is in (for example: telling a sidecar container what namespace the Pod is running in) providing read-only access to data in a different container image Data sharing can be between different local processes within a container, or between different containers, or between Pods.