Steven Fitzpatrick 3257ed1db8 Remove the Elasticsearch Wait job from the chart
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
2020-07-16 10:16:23 -05:00
2020-07-10 02:34:13 +00:00
2020-06-11 23:29:42 -05:00
2020-06-17 13:13:53 -05:00
2020-06-11 23:29:42 -05:00
2020-07-09 16:02:59 +00:00
2019-04-19 19:34:11 +00:00
2020-05-07 02:11:15 +00:00
2020-04-11 15:26:50 +02:00
2018-05-15 13:04:28 -05:00
2020-06-11 23:29:42 -05:00

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
Repository for OpenStack Helm infrastructure-related code
Readme 67 MiB
Languages
Smarty 86.7%
Shell 11%
Python 1.7%
Jinja 0.3%
Makefile 0.3%