Repository for OpenStack Helm infrastructure-related code
abb5e0f713
This begins to split the fluent-logging chart into two separate charts, one for fluentbit and one for fluentd. This is to help isolate each chart and its dependencies better, and to treat each service as its own entity. This also moves the job for creating Elasticsearch templates to the Elasticsearch chart, as the elasticsearch chart should have ownership of creating the templates for its indices. This also performs some general cleanup of values keys that are not currently used Change-Id: I827277d5faa62b8b59c5960330703d23c297ca47 Signed-off-by: Steve Wilkerson <sw5822@att.com> |
||
---|---|---|
calico | ||
ceph-client | ||
ceph-mon | ||
ceph-osd | ||
ceph-provisioners | ||
ceph-rgw | ||
doc | ||
elastic-apm-server | ||
elastic-filebeat | ||
elastic-metricbeat | ||
elastic-packetbeat | ||
elasticsearch | ||
etcd | ||
falco | ||
flannel | ||
fluentbit | ||
fluentd | ||
gnocchi | ||
grafana | ||
helm-toolkit | ||
ingress | ||
kibana | ||
kube-dns | ||
kubernetes-keystone-webhook | ||
ldap | ||
libvirt | ||
lockdown | ||
mariadb | ||
memcached | ||
mongodb | ||
nagios | ||
nfs-provisioner | ||
openvswitch | ||
playbooks | ||
podsecuritypolicy | ||
postgresql | ||
prometheus | ||
prometheus-alertmanager | ||
prometheus-kube-state-metrics | ||
prometheus-node-exporter | ||
prometheus-openstack-exporter | ||
prometheus-process-exporter | ||
rabbitmq | ||
redis | ||
registry | ||
roles | ||
tiller | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
Makefile | ||
README.rst | ||
setup.cfg | ||
setup.py | ||
tox.ini |
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 Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.