Large game server container images

[dgkanatsios]

Some game server container images can be pretty large, i.e. several GB. This can result in container images being slow to download and extract. Thus, Pods that reference large containers on AKS will take some time to download and start. Azure Container Registry has introduced project Teleport which is coming soon to AKS in public preview and will greatly decrease time needed to start Pod off a large container image. We should

• document Teleport once it becomes available for AKS
• document alternative ways, e.g.
  • having the game server container image containing only the executable binaries and have the rest of the files located on an Azure File Share and mounted on each Pod
  • having game server asset files copied from a central location to every Node and mounted by each GameServer Pod. We could do this with a DaemonSet but we'd need a way to signal that the Node is unschedulable as it downloads and extracts the files (so we don't schedule GameServer Pods before the files are there).

[dgkanatsios]

We should document mounting asset files the way this is done on MPS, e.g. mounted on "/data/DownloadedAssets" on every container instance.

[dgkanatsios]

Azure Disk CSI driver might be interesting to look at: https://github.com/kubernetes-sigs/azuredisk-csi-driver

Specifically the shareddisk feature: https://github.com/kubernetes-sigs/azuredisk-csi-driver/tree/master/deploy/example/sharedisk

[dgkanatsios]

We should also mention support for AKS teleport, when it's on public preview. https://github.com/Azure/AKS/issues/1785