Comments on: Blue-green deployment with a database on Kubernetes https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/ Java, Spring, Kotlin, microservices, Kubernetes, containers Mon, 12 Jul 2021 10:41:53 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: piotr.minkowski https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/#comment-1182 Mon, 12 Jul 2021 10:41:53 +0000 https://piotrminkowski.com/?p=9450#comment-1182 In reply to Robert Reeves.

Hi!
Thanks for your updates.

]]> By: Robert Reeves https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/#comment-1168 Wed, 30 Jun 2021 17:31:30 +0000 https://piotrminkowski.com/?p=9450#comment-1168 Hi, Piotr!

Great post! I have found some issues with some of the PG config and LB config. Also found a SQL error in the V2 config map. I opened a PR: https://github.com/piomin/sample-spring-bluegreen-with-db/pull/2.

Thanks!

Robert @ Liquibase

]]> By: piotr.minkowski https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/#comment-1029 Sat, 27 Feb 2021 22:52:34 +0000 https://piotrminkowski.com/?p=9450#comment-1029 In reply to Michal Kunikowski.

Well, I also think that in general, you should not do incompatible changes from prev version to the next version 🙂
Don’t focus on that example. I know that in that particular case create a new column, and copy data is a better choice. I just needed a simple scenario with incompatible changes. I can imagine any different case – like let’s say we added a unique key on a column, and we also need to prevent from adding duplicates on the app side etc.

]]> By: Michal Kunikowski https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/#comment-1028 Sat, 27 Feb 2021 21:53:34 +0000 https://piotrminkowski.com/?p=9450#comment-1028 Hmmm. lets say that migration script takes 10 minutes. If you are doing incompatible changes from prev version to next version does it means that prev version could have 10 minutes errors?
I think in general you should not do incompatible changes from prev version to next version.
What if you need do fast rollback if service version two has some bugs.

IMO should be like this
ver1 -> ver2 -> add new column. copy data from old column
ver 2 -> ver 3 -> delete old column from ver1

]]> By: piotr.minkowski https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/#comment-1019 Fri, 19 Feb 2021 12:43:46 +0000 https://piotrminkowski.com/?p=9450#comment-1019 In reply to jkornata.

It depends on how long does it take to modify the Istio rule after running the Liquibase script 🙂

]]> By: jkornata https://piotrminkowski.com/2021/02/18/blue-green-deployment-with-a-database-on-kubernetes/#comment-1018 Fri, 19 Feb 2021 07:47:24 +0000 https://piotrminkowski.com/?p=9450#comment-1018 Won’t we have a possible downtime/read errors in v1 if we do the switch in VirtualService manually? There will be a moment in time when the database is already updated, v2 won’t accept traffic and v1 uses incorrect schema? Am I wrong?

]]>