You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Sergio Chong (Jira)" <ji...@apache.org> on 2025/03/19 16:17:00 UTC

[jira] [Created] (FLINK-37515) FLIP-503: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)

Sergio Chong created FLINK-37515:
------------------------------------

             Summary: FLIP-503: Blue/Green Deployments for Flink on Kubernetes: Phase 1 (basic)
                 Key: FLINK-37515
                 URL: https://issues.apache.org/jira/browse/FLINK-37515
             Project: Flink
          Issue Type: New Feature
          Components: Kubernetes Operator
    Affects Versions: kubernetes-operator-1.11.0
            Reporter: Sergio Chong


We identified the need for a solution to have minimal “downtime” when re-deploying pipelines. This is the case when the startup times are high and lead to downtime that’s unacceptable for certain workloads.

Flink pipelines require the data stream flow to be halted during deployment operations. For some cases stopping this data flow could have a negative impact on downstream consumers.

A Blue/Green deployment architecture can help overcome this issue by starting a second identical pipeline along side the main one and switching over to it when the desired criteria is met.

This JIRA represents support for an initially simple Blue/Green deployment as a new feature for the Flink Kubernetes Operator.



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