diff options
| author |   Sylvain Desbureaux <sylvain.desbureaux@orange.com> | 2019-12-27 11:06:14 +0100 |
|---|---|---|
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | 2019-12-27 11:06:14 +0100 |
| commit | d398482dc9eb34d44c1997eeb2650880ded350d7 (patch) | |
| tree | 6b7ac7abf9f219c9f848171d3fba22cc8a038ac0 /docs/cluster.yml | |
| parent | 78211d7aabf6d7612e5c94cecbd40eb3c29a48d6 (diff) | |
[DMaaP] Wait for AAF locate before AAF config
AAF config needs to have aaf locate service up and running in order to
work properly (if not, it won't really crash but won't have done the
real work).
As per
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#understanding-init-containers,
"Each init container must complete must complete successfully before the
next one starts".
Adding a wait for readiness container before aaf config init containers
should then do the job.
Change-Id: Ida047728e4f14320ada8052c707b458450f4923b
Issue-ID: DMAAP-1362
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'docs/cluster.yml')
0 files changed, 0 insertions, 0 deletions