Rolling upgrade on Kubernetes from JGroups 4 to 5

[Chintan Mohan Rohila]

Dear community,

We are planning JGroups 4.2.26/KUBE_PING 1.0.17 to Jgroups 5.4/ KUBE_PING 2.0.2  upgrade on a Kubernetes cluster without a downtime.

Since, channels running on JGroups 4 and 5 together can't form a cluster, so as suggested in https://github.com/jgroups-extras/upgrade-common we are trying to use the upgrade server approach, but JGroups channels from v4 and v5 are not able to form a single cluster and not able to find a way to achieve it in the current documentation of upgrade server.

If someone has implemented or has a working procedure for a similar rolling upgrade on a Kubernetes cluster then please share.

Thanks and Regards.

Chintan Rohila

[Bela Ban]

upgrade-jgroups / upgrade-common currently only support upgrades between 5.2.x and 5.3.3. It should be simple to create 2 branches for 4.x and 5.x in upgrade-jgroups.

Note that the older RollingUpgrades repo [1] supports upgrades between 4.x and 5.2.

The latest effort is JGraaS [2], but I've not worked on it for quite a while, being side tracked by other stuff.

In the first 2 cases, the difficulty will be to upgrade KUBE_PING: it requires a certain JGroups version and depends on the returned JSON being compatible between 1.x and 2.x.



[1] https://github.com/jgroups-extras/RollingUpgrades
[2] https://github.com/jgroups-extras/jgraas-common

--
You received this message because you are subscribed to the Google Groups "jgroups-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jgroups-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jgroups-dev/99c271b3-f4df-440a-a505-7640a5242012n%40googlegroups.com.

-- 
Bela Ban | http://www.jgroups.org