>
> 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
ha
> If the container is removed, you need to do a cleanallruv on shutdown, and
> purge the
> volume so the replica ID can be reused. So you likely only have autoscaling
> to *grow*
> covered, but not to shrink.
Yes, that's true. I hadn't thought of autoscaling for shrink. Probably a part
of next
> A simple way to consider this is that every 389 instance in a container is a
> read-only
> replica, then you simplfy your system a lot (RO instances have a replica ID
> of 65535 (I
> think)). This way on startup/shutdown you just re-init the RO from an
> external hub or
> similar, then you don
Hello William,
Thank you for the advice.
> Hey there!
>
> Great to hear you want to use this in a container. I have a few things to
> advise here.
>
> From reading this it looks like you want to have:
>
> [ Container 1 ][ Container 2 ][ Container 3 ]
> |
Hello,
I plan to run 389ds in containers (docker image on kubernetes), with a
multi-master replication setup, as described below.
Setup:
- Deployment: I'm using kubernetes statefulsets so the containers get created
with the same name
- Name resolution: A headless service is created, so the cont
