[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6673: -------------------------------------- Description: There are 2 mechanisms which seems to do the same but are totally different: * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure. was: Currently Kubernetes Rolling Upgrades might damage the cluster and cause data loss. The only way to avoid that is to use a Cache Store. We should instrument the Rolling Upgrades mechanism and indicate when it is safe to scale the cluster in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)