I have run into at least one change that is required by the user to make in order to migrate from 1.5.3 to 1.6.0 for peerpods.  There are a number of other doc changes that will provide additional information to make migration easier, but we need fully document any actions that customers need to take in order to upgrade with an existing configuration and workloads.  We can use this issue to collect all the necessary information.