[
https://issues.apache.org/jira/browse/FLINK-37515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032834#comment-18032834
]
Sergio Chong commented on FLINK-37515:
--------------------------------------
[~bli] No ticket yet on the Advanced phase, so far only documented [FLIP-504.
|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=337677650]I'll
be creating the ticket along with a Draft PR so we can get feedback from the
community, aiming next week.
+1 on fixing FLINK-38548 , will follow up as well.
> 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
> Priority: Minor
> Labels: pull-request-available
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> 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)
