Back in 2020, there was a Flink Forward talk [1] about how Lyft was
doing blue green deployments. Earlier (all the way back in 2017)
Drivetribe described [2] how they were doing so as well.
David
[1] https://www.youtube.com/watch?v=Hyt3YrtKQAM
[2] https://www.ververica.com/blog/drivetribe-cqrs-ap
Definitely our intent is to start with an in house specific Blue Green
operator and once we will reach some level of confidence we will open a
FLIP to discuss it.
Nicolas
On Thu, Aug 31, 2023 at 10:12 AM Gyula Fóra wrote:
> The main concern as we discussed in previous mailing list threads befor
The main concern as we discussed in previous mailing list threads before is
the general applicability of such solution:
- Many production jobs cannot really afford running in parallel (starting
the second job while the first one is running), due to data
consistency/duplications reasons
- Exactly
Thanks Gyula for your feedback.
We were also thinking of relying on such a solution, creating a dedicated
crd/operator to manage this BlueGreenFlinkDeployment.
Good to hear that it could be incorporated later in the operator.
Will let you know once we will have something to share with you.
Nicol
Hey!
I don't know if anyone has implemented this or not but one way to approach
this problem (and this may not be the right way, just an idea :) ) is to
add a new Custom Resource type that sits on top of the FlinkDeployment /
FlinkSessionJob resources and add a small controller for this.
This new
