Closed ddgenome closed 5 years ago
After discussing with the team, we determined that the cost/benefit ratio for this workaround is upside down.
To migrate our existing deployments to the new style, we can just delete existing deployments, orphaning its child resources so they are not also deleted. Anytime after the replacement deployment is created after the next push, we can just delete the orphaned resources since one the new version registers, the old one will stop receiving events.
When migrating from k8-automation to sdm-pack-k8s, the label selectors of the deployment will change. Unfortunately, the label selectors are immutable. We need to figure out a way to allow for a smooth transition for existing deployments.