Regarding the feature request below: Currently, Harness cannot transition a release from a Rolling Deployment to BlueGreen without starting a new deployment from scratch. This can be challenging in scenarios where multiple deployment types are required. A workaround we've used involves manually patching the services to ensure that the label color is available when the blue/green deployment begins.
I propose an enhancement to smooth this transition from Rolling Deployment to Blue Green Deployment within Harness. Perhaps an initial validation step could prepare the environment (namespace) for the application, allowing a rolling update to convert to blue-green without manually addressing the nuances of this deployment difference.
Having this feature could allow DevOps teams to more straightforwardly control deployments and maximize each one based on scale and internal needs, enhancing the usability of the Harness platform.