Okay, that looks really good. I read this and the example setup instructions they have. Something I missed was a way to coordinate or notify into a running container about the creation of another one. For example, we have ldap-0 and ldap-1, we need to notify ldap-0 that ldap-2 was just brought online (or taken offline). Did I miss how to trigger an event like this? As usual, do you think there would be value in upstream providing template yml files for this kind of setup/configuration? Thanks! > On 18 Jun 2019, at 11:12, Olivier JUDITH <gnulux@xxxxxxxxx> wrote: > > You can read more here > > https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/ > > Le mar. 18 juin 2019 à 10:44, William Brown <wbrown@xxxxxxx> a écrit : > > > > On 17 Jun 2019, at 16:25, Olivier JUDITH <gnulux@xxxxxxxxx> wrote: > > > > From my understanding readiness operates when the pod starts. > > If it doesn't reach the replica your pods will never initialize. > > An option (for k8s) can be another container (in the pod) "389-ds-headless" which will do all the steps required to enable replication. > > > > > Okay - how does the content of secrets.yaml get sent to the process running in the container? > > By files or by variables but are always present in the container. > > > > To enable replicas , k8s provides StatefullSet controller which is better to manage multiple instances/replication. > > Is there some documentation on this I could have a look at? It would be good for me to understand to help advise on this, because dynamic scaling of replicas is something I'd really love to see supported in k8s and upstream so we can provide a really good experience for people :) > > I think it's time for me to setup k8s at home again to learn this ..... > > > > > Regards > > > > > > Le lun. 17 juin 2019 à 13:57, aravind gosukonda <arabha123@xxxxxxxxx> a écrit : > > > > > > Is there also a way in k8s that when an event occurs (IE a new container is launched in a > > > pod) that a program can be called in existing containers? (This way we can automate > > > replica addition/removal) > > > > > What I'm planning to do is to use readiness probes, which can be scripts, to handle dynamic configuration of replicas. I haven't seen any way that enables existing containers to know when a new container has been launched or an old container deleted. > > > > Regards, > > Aravind G > > _______________________________________________ > > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx > > — > Sincerely, > > William Brown > > Senior Software Engineer, 389 Directory Server > SUSE Labs > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
