Thanks for the great question @gvde. There is not an available migration path yet for content proxy’s and existing proxies running Pulp 2 will continue to work. The teams have been discussing the easiest path forward for users with respect to content proxies. Those discussions center around two approaches, to follow, and we’d love your input as a user which you would prefer. Keep in my mind we are balancing the amount of work, overhead and complexity for the user with the needs of the user based on their setups.
-
No in-place upgrades. Deploy new content proxy with Pulp 3, and sync it.
a) With a new hostname, migrate clients
b) With the existing hostname, switch DNS -
In-place content proxy upgrades with content migration. This may require additional resources on the content proxy host as both Pulp 2 and Pulp 3 (along with their databases) would need to run.