You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Oleg Vorobev (Jira)" <ji...@apache.org> on 2022/09/05 14:02:00 UTC

[jira] [Created] (FLINK-29199) Support blue-green deployment type

Oleg Vorobev created FLINK-29199:
------------------------------------

             Summary: Support blue-green deployment type
                 Key: FLINK-29199
                 URL: https://issues.apache.org/jira/browse/FLINK-29199
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
         Environment: Kubernetes
            Reporter: Oleg Vorobev


Are there any plans to support blue-green deployment/rollout mode similar to *BlueGreen* in the [flinkk8soperator|https://github.com/lyft/flinkk8soperator] to avoid downtime while updating?
The idea is to run a new version in parallel with an old one and remove the old one only after the stability condition of the new one is satisfied (like in [rollbacks|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.1/docs/custom-resource/job-management/#application-upgrade-rollbacks-experimental]).
For stateful apps with {*}upgradeMode: savepoint{*}, this means: not cancelling an old job after creating a savepoint -> starting new job from that savepoint -> waiting for it to become running/one successful checkpoint/timeout or something else -> cancelling and removing old job.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)