3257ed1db8
The elastic-cluster-wait job was meant to serve as a dependency check for a couple of other jobs, such that when this wait job was complete the other jobs could procede successfully. This goal can be achieved by using our HTK init container's dependency check however. The two jobs that waited on this wait job just need to use the elasticsearch API, which is available once the `elasticsearch-logging` service has endpoints. Change-Id: I87e1c1fe3d61680a73701d48f85e5c48c11b6325
38 lines
1.1 KiB
YAML
38 lines
1.1 KiB
YAML
---
|
|
pod:
|
|
env:
|
|
client: null
|
|
data: null
|
|
master: null
|
|
mandatory_access_control:
|
|
type: apparmor
|
|
elasticsearch-register-snapshot-repository:
|
|
register-snapshot-repository: runtime/default
|
|
init: runtime/default
|
|
elasticsearch-master:
|
|
elasticsearch-master: runtime/default
|
|
init: runtime/default
|
|
memory-map-increase: runtime/default
|
|
elasticsearch-data:
|
|
elasticsearch-data: runtime/default
|
|
init: runtime/default
|
|
memory-map-increase: runtime/default
|
|
elasticsearch-client:
|
|
elasticsearch-client: runtime/default
|
|
init: runtime/default
|
|
memory-map-increase: runtime/default
|
|
apache-proxy: runtime/default
|
|
prometheus-elasticsearch-exporter:
|
|
elasticsearch-exporter: runtime/default
|
|
init: runtime/default
|
|
elasticsearch-test:
|
|
init: runtime/default
|
|
elasticsearch-helm-tests: runtime/default
|
|
create-elasticsearch-templates:
|
|
create-elasticsearch-templates: runtime/default
|
|
init: runtime/default
|
|
elasticsearch-verify-repositories:
|
|
elasticsearch-verify-repositories: runtime/default
|
|
init: runtime/default
|
|
...
|