https://bz.apache.org/bugzilla/show_bug.cgi?id=66660
--- Comment #6 from Remy Maucherat <r...@apache.org> --- (In reply to Diego Rivera from comment #4) > (In reply to Mark Thomas from comment #2) > > It looks like it needs more Javadoc and some documentation but I suspect > > using the k8s specific membership provider would be a better solution: > > > > https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalina/tribes/ > > membership/cloud/package-summary.html > > We're very much trying to avoid granting access to the K8s infrastructure to > our pods, for security reasons. I don't really understand the security concern since this is so granular, and it seems the whole point. But anyway, there is also the K8 DNS based membership provider: https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalina/tribes/membership/cloud/DNSMembershipProvider.html I personally prefer the regular provider since it is more reliable, though. > I saw that class and it piqued my interest, but quickly fizzled when I saw > how it works. We have the same conundrum: when it fetches the membership > list, only one pod exists (the one being booted up), so we'd be back to > square one regarding "expected members which don't yet exist or aren't yet > available". > > The problem is that the StaticMember expects all members to exist upon > instantiation, whereas this may not always be the case. Sure, but you're asking for a dynamic static membership list here, basically. -- 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
