>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. Regards Le lun. 17 juin 2019 à 13:57, aravind gosukonda <arabha...@gmail.com> 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@lists.fedoraproject.org > To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org >
_______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
