Hi:
At the moment we perform TCP health check via F5 on ports 389/636 (historical
inheritance) – which isn’t sufficient for HA.
We are moving to an env where NSX and F5 may co-exist – and have an opportunity
to re-work the LB health check for HA (on existing F5 and upcoming NSX).
If running
>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
hi,
I'm still evaluating some options to securize dynamic nodes and I have some
questions regarding certutil and nss databases:
Can I create NSS databases on any directory/server and then move files to
"/etc/dirsrv/slapd-instance_name" ?
If cert8.db and key3.db files are found in that
>
> 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
