Documentation for production deployments

README.md

@@ -75,6 +75,22 @@ are granted access to `microk8s` commands. To add a user to that group:
 sudo usermod -a -G microk8s <username>
 ```
 
+#### Production Installation
+
+The Snapcraft package manager is the only way to install microk8s. This platform auto-updates packages without user interaction to track authors security patches and new point releases for a channel. It is recommended to pick a channel during installation with `--channel=x.xx/stable`, as upstream Kubernetes releases have been known to break during upgrades. If you do not specify a channel, auto-updates will track the latest stable release, which is likely not what you want for production deployments.
+
+If your production deployment can handle unattended upgrades without a schedule, you should not have to modify snapd. If you have regular maintenance windows, you can [schedule unattended updates for a snap](https://snapcraft.io/docs/keeping-snaps-up-to-date). 
+
+As of version 1.19 a mission critical installation should use the High Availability option, which requires three or more physical nodes. Ensure these nodes auto-upgrade schedules are staggered because if two nodes go down at the same time the cluster will be unavailable.
+
+An alternative to upgrading or installing an HA cluster for mission critical installations is to disable all unattended updates. To do this, download and install a snap in "dangerous" mode to pin a version. This gives the user the ability to control the upgrade and security patching schedule. Do this with the following combination
+
+```
+snap download microk8s --channel=version/label 
+# where version is a valid version number and label is stable or edge
+sudo snap install microk8s_xxxx.snap --dangerous --classic 
+# where xxxx is the release number.
+```
 
 #### Kubernetes add-ons