
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
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on freenode
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.
Description
Languages
Smarty
86.7%
Shell
11%
Python
1.7%
Jinja
0.3%
Makefile
0.3%