https://bz.apache.org/bugzilla/show_bug.cgi?id=66660
--- Comment #16 from romain.manni-bucau <rmannibu...@gmail.com> --- Sounds like what you want is to start the cluster only after which means you assume that none of the N-1 pods serve anything before pod N is started. Think this is a high assumptiong for tomcat. If not, DNS service sounds like a correct compromise if you don't want to watch kubernetes API to not have to setup a service account. Last option remains to implement a custom membership strategy, with the specificty of your deployment I think it can be a not so bad option and it could even make sense to use tomcat cluster events for the instance X to notify [1;X-1] instance it is started and join the cluster (a bit like multicast impl but without multicast need)....but really think this is a very particular deployment mode and I'm not sure it is sane to propagate or encourage to be honest. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
