<p>I currently have a dockerized application that I'd like to have the deployment model of multi-tenancy. The end goal for me is to be able to deploy the multiple application instances without the need to spin up a VM for every instance.</p>
<p>I've looked at Kubernetes, and I'm looking at pods for now, but would like some practical guidance as I'm inexperienced in Kubernetes.</p>
<p>How would I, if possible, practically do this? And how would the deployment look like?</p>

Bryan
<p>In Kubernetes, you may isolate your tenants by using namespaces. Each tenant will get its own namespace to spin up pods and other namespace scoped objects. Furthermore, you can define <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/" rel="nofollow noreferrer">role and rolebinding</a> and implement RBAC to grant access to a particular namespace.</p>
<p><strong><a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/" rel="nofollow noreferrer">Namespaces</a></strong></p>
<blockquote>
<p>In Kubernetes, namespaces provide a mechanism for isolating
groups of resources within a single cluster. Names of resources need
to be unique within a namespace, but not across namespaces.
Namespace-based scoping is applicable only for namespaced objects
(e.g. Deployments, Services, etc) and not for cluster-wide objects
(e.g. StorageClass, Nodes, PersistentVolumes, etc).</p>
</blockquote>
