https://bz.apache.org/bugzilla/show_bug.cgi?id=66660
--- Comment #4 from Diego Rivera <diego.riv...@armedia.com> --- (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 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. -- 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
