I am trying to upgrade Ververica Platform to version 2.4 or later. The names of some of my deployments are changed during the upgrade, and I cannot change them back. What is the reason here? How can I preserve those names during the upgrade?
Note: This section applies to upgrading Ververica Platform 2.0-2.3.x to 2.4 or later.
Starting from Ververica Platform 2.4.0, deployments in Ververica Platform are name-addressable. The `metadata.name` of a deployment serves as a unique identifier. Therefore, the name must match a `[a-z0-9]([-a-z0-9]*[a-z0-9])?` pattern and cannot be changed after the deployment is created. The field `metadata.displayName` can be used for human-readable names, which are displayed in the Web UI.
If you want to preserve the original deployment names, you should change the deployment names in the version before 2.4 to the ones that match the `[a-z0-9]([-a-z0-9]*[a-z0-9])?` pattern. This has to be done before you go through an upgrade! If you have already performed the upgrade, you need to fall back to the previous version, change the deployment names, then upgrade again.
Improvements to REST API since Ververica Platform 2.4.0
Ververica Platform 2.4.0 Migration Compatibility