Example manifests need to protect kip's internal storage/state

[justnoise]

Kip keeps an internal storage of:

• Identity
• CA
• Pods and Nodes

If a kip deployment is restarted without preserving the PersistentVolume kip's state is stored on, all pods will be restarted and the previous kip cells will be orphaned in the cloud since kip's identity will be recreated as well. We've talked about this in other discussions in slack.

Todo:

• Ensure our deployment scripts recreate the persistent volume that stores kip's data
• Explore using a statefulSet as a method of ensuring virtual-kubelet identity. That would require creating a cluster identity in the API server when starting up kip and then using that plus the stateful identity to identify cloud resources that belong to an instance of a kip instance.